Leaving Finale, Order Manager or Sellercloud: A Switch Plan

Descartes Systems Group now owns three products that run inventory and orders for a brand. It bought Sellercloud in October 2024, Finale Inventory in August 2025, and Extensiv, which includes the old Skubana as Extensiv Order Manager, on 1 September 2026. If you run on one of them, you are probably wondering whether you are about to be moved, and where to.

This page is the switch plan I use for all three: what moves over, how long it takes, what you keep, and what does not come across cleanly. I run SKU.io, which competes with all three, so weigh it accordingly. I have kept what is public apart from what customers told me, and said which is which. Product-specific detail is on the Finale page, the Order Manager migration plan and what we know about the Order Manager end of life.

Written 12 November 2026. Vendor prices are from each vendor’s own pricing page on the dates in “How we checked this page” below. All figures USD.

Why are Descartes customers looking now?

Because one company now owns three overlapping products, and only one of them looks like the reason it bought.

• Sellercloud, bought in October 2024. Its pricing page, as read on 29 October 2026, lists Essentials from $1,349 a month and Growth from $1,998, with plans “typically offered through an annual subscription.”
• Finale Inventory, bought on 4 August 2025. Its pricing page lists Essentials from $499 a month, Growth from $799, and API and EDI access only on Enterprise, which is quote-only.
• Extensiv, bought on 1 September 2026 for about $120 million. Descartes described it entirely as 3PL warehouse software. Order Manager, the brand-side product that used to be Skubana, was not mentioned.

On its earnings call ten days later, Descartes told investors to expect revenue attrition from the part of Extensiv outside its 3PL warehouse core, early in its next fiscal year. Since then Extensiv Order Manager customers are being told the product is ending. On a recorded call on 6 November, an operations lead relayed what their Extensiv rep had said: “They’re sunsetting the product and it’s going to try and push us on to Finale.” On 12 November, another Order Manager customer wrote on a demo booking form that Extensiv is deprecating Order Manager. Descartes has not announced either in public. Those are customers’ accounts, not an announcement, and the end-of-life page keeps the full record.

Finale customers are mostly not being pushed anywhere. They are deciding whether the product they bought before the sale is still the product they are paying for after it. The entry price moved from $99 to $499, barcode scanning now sits in the $799 plan, and the API is on a quote. The Finale page has the detail and what former users said on recorded calls.

What moves over to a new system?

Almost everything you would want to keep, as long as you export it while you still have full access. None of the three has a one-click route into SKU.io. Your data comes across through SKU.io’s documented imports, and the table below is the order it loads in.

What	How it lands in SKU.io	What to watch
Products: SKU, name, barcode, cost, weight, dimensions	The product import, every column listed in the importable columns reference	Duplicate SKUs that both have stock behind them
Bundles and kits with their components	Bundles and kits, loaded before any order	Load today's recipe, not an old one
Suppliers with lead times and costs	The supplier import	Supplier SKUs that differ from yours
Stock on hand, by warehouse	One initial count per warehouse, dated to your start date, with a quantity and unit cost per product	Units assigned to no warehouse
Open purchase orders, only what has not arrived	The purchase order import, arriving as drafts you check first	Partly received POs: move only the remainder
Wholesale customers	The customer import	Customer pricing kept in notes
Cost and count history from before the switch	History before go-live: past counts and supplier invoices in their own register, so your accountant still gets monthly cost of goods sold	You need at least one full count, usually year end
Past sales orders	Quoted as a one-off item on its own line before you sign	Returns of orders placed before the switch

Where the export comes from depends on what you are leaving. Order Manager publishes its API documentation at developer.extensiv.com, so anything its screens won’t hand you can be pulled through it. Sellercloud lists API access on every plan. Finale is the hard one: its pricing page puts API access on Enterprise only, and its developer site says integration partners can use the API for any Finale customer, while the customer can only on the top plan. On Essentials or Growth, plan on screen exports, and ask your Finale rep before your renewal date which lists you can export.

How long does a switch take?

Two different clocks run here, and vendors usually quote only the short one.

Setting SKU.io up takes days. Onboarding is hands-on, has no fee, and I am in it. Products, bundles, warehouses and channels can be loaded and connected in that time.

The switch takes four to eight weeks for a multichannel brand with bundles and a 3PL, from first export to the day the old system stops routing orders, plus a buffer. The data is not what makes it slow. These three things are:

1. Duplicate SKUs. When I moved a bar-tools brand off Extensiv this January, their catalog had duplicate SKUs with real stock behind both records. Somebody who knows the products has to decide which survives and where the stock goes. That took the customer several sessions, and no import tool could have done it for them.
2. Your 3PL’s API. The same switch stalled on a 3PL whose orders endpoint had no pagination, so pulling history took far longer than it should have. Ask your 3PL early how they hand over order history.
3. The overlap. A few days of both systems importing orders, compared every morning, before fulfillment moves over.

If your contract runs into 2027, you have time to choose properly, but not time to wait and see. Don’t plan the cutover for peak season.

What do you keep?

More than most switchers expect. The things that are hard to rebuild stay where they are:

• Your sales channels. The same Shopify, Amazon, Walmart, TikTok Shop and wholesale accounts reconnect to SKU.io. A product carries its listings on each channel as mappings, so one physical SKU has one stock figure.
• Your SKU codes. You keep your own. The migration is the moment to remove duplicates, not to renumber.
• Your 3PL. SKU.io connects to ShipBob, ShipHero, Shipfusion and VeraCore directly, and to other warehouse systems through Trackstar. If your 3PL runs Extensiv’s own warehouse software, the old 3PL Central, Trackstar is the route. It is passed through at Trackstar’s price, and it starts billing when that connection goes live, which is usually at launch but can be before it.
• Your books. QuickBooks Online or Xero stays your accounting system. SKU.io posts to it, it does not replace it.
• Your EDI, if it runs through SPS Commerce. The SPS Commerce connection is built. If your trading partners connect another way, bring the list to the call.
• The tools you built on the old API. Some Order Manager and Sellercloud teams have their own scripts on the API. SKU.io’s API is in every plan, documented in public at developer.sku.io, so those tools have somewhere to point.

What does not come across cleanly?

Four things, and I would rather you hear them now than in week two.

• There is no one-click importer. For Order Manager, SKU.io’s team runs a migration tool with you from your export files. For Finale and Sellercloud, your data comes through the imports above and, where you have it, the old system’s API.
• Average cost becomes one opening cost. Finale documents average costing, so there is no record of each buy’s cost to bring across. Your opening stock carries one unit cost per product per warehouse. From the first receipt in SKU.io, every buy is its own FIFO layer.
• Order history is a separate line. Past sales orders are quoted on their own before you sign, because how much you bring back changes the work.
• Automations get rebuilt, not copied. Order rules and routing you set up over years have to be set up again, as workflows and routing in SKU.io. Write down the ones you rely on before you start.

Which Descartes product are you leaving?

Extensiv Order Manager (Skubana). You have the clearest deadline: your contract end date, until Extensiv tells you in writing that access continues past it. Start with what we know about the end of life, then the migration plan, which covers Order Manager’s exports step by step. The Skubana alternatives page has why operators left it before any of this.

Finale Inventory. Nobody has announced an end for Finale, so the question is whether it still fits. The usual reasons to move, from former users on recorded calls, are cost that never settles because it is averaged, product screens buried under order-level noise at high volume, and an API you can’t reach on your plan. All three are on the Finale page.

Sellercloud. Sellercloud’s Growth plan adds the Skustack mobile module for picking, packing and receiving, and its API is on every plan, which is more than Finale offers. The trade-off buyers name is complexity. The founder of a $10M to $50M multichannel brand who looked at it in 2025 put it this way: “Seller Cloud gets close but… there’s way too much complexity. You have to press through 10 different things.” If you run your own warehouse and need that depth, Sellercloud may be the right move inside Descartes. If you use a 3PL and your problem is cost, channels and the books, it is a lot of system to pay $1,349 to $1,998 a month for.

If your rep is steering you to another Descartes product, ask one question before you sign: is this a long-term home, or the next product to be consolidated? You are being moved once because of a portfolio decision. Make sure you aren’t moved twice. TradeGecko customers who took Intuit’s suggested path in 2022 were shut down again fourteen months later. The rest are on the inventory software graveyard.

Who should not switch to SKU.io?

If your system works, your stock numbers are believed, and your contract runs for years with nobody telling you it ends, stay. A switch costs your team’s time, and that cost is real.

If you sell under about $1M on one channel, Zoho Inventory or inFlow will do the job for a fraction of the price. If your complexity is production runs and bills of materials rather than channels, look at Katana. And if you run a large warehouse of your own and want one vendor for picking and orders, Sellercloud’s warehouse depth may matter more to you than anything on this page.

SKU.io fits $1M to $50M multichannel brands: Shopify plus Amazon, Walmart, TikTok Shop or wholesale, with bundles and kits, a 3PL or several warehouses, and QuickBooks Online or Xero on the books. Pricing starts around $1,000 a month and scales with orders and SKUs. There are no onboarding fees, and I give every demo myself.

Frequently asked questions

Does Descartes own Finale, Sellercloud and Extensiv? Yes. Descartes Systems Group bought Sellercloud in October 2024, Finale Inventory on 4 August 2025, and Extensiv, including Extensiv Order Manager (formerly Skubana), on 1 September 2026.

Is Extensiv Order Manager being discontinued? Descartes has not announced a date. Order Manager customers are being told it is ending: in November 2026 they told me so on a recorded call and on a demo booking form. Plan for your contract end date.

How long does it take to switch off Finale or Order Manager? Setting up SKU.io takes days. For a multichannel brand with bundles and a 3PL, plan on four to eight weeks from the first export to cutover. Cleaning up duplicate SKUs is usually the slowest part.

Can I keep my 3PL if it runs Extensiv’s warehouse software? Yes. SKU.io reaches Extensiv’s 3PL warehouse software, the old 3PL Central, through Trackstar, which is passed through at Trackstar’s price.

Will I lose my cost history? No. Opening stock loads with a unit cost per product per warehouse, and the History before go-live register keeps your past counts and supplier invoices so monthly cost of goods sold before the switch can still be worked out. From the switch on, every receipt is its own FIFO cost layer.