If your buyers order in spreadsheets, your ERP is in the wrong place
A growing fashion retailer ran its books in QuickBooks, its stock in Fishbowl, and its vendor orders in spreadsheets, because its setup couldn't take an order by size and color. Cateran moved the business onto Business Central online, warehouse first and then the stores, in about nine months.
Client: multi-store fashion retailer with an online store. Moved to: Microsoft Dynamics 365 Business Central online. Operating model: one central warehouse supplying the stores, every style in size and color variants, and an in-house point of sale.
Executive summary
- The problem. Apparel is bought by style, in a grid of sizes and colors. QuickBooks couldn't take an order that way, so buyers placed vendor orders in spreadsheets. The business's biggest commitments sat outside the books, and inventory was split between two systems that had to be kept in sync.
- The answer. One system for finance, inventory and purchasing. Business Central online holds the ledger and the stock in one database, supports multiple locations, transfers and item variants as standard, and with a third-party extension takes vendor orders in a size and color grid.
- The delivery. A three-person Cateran team: lead architect, functional consultant and data migration specialist. They went live at the central warehouse first, then brought the stores on a few at a time, and built a custom integration to the retailer's homegrown point of sale.
- The result. Warehouse and inventory live in five months, every store live four months later. All data came across from QuickBooks and Fishbowl, and stock started in Business Central at counted, not synced, quantities.
1. The real problem was buying, not bookkeeping
Most retailers think of QuickBooks as an accounting problem. Here the pain was upstream. A fashion buyer thinks in styles: one dress, ordered in five sizes and four colors, with a quantity in each cell. QuickBooks had no way to enter a size and color matrix on a purchase order.
So the buyers worked in spreadsheets. That kept the business's most important commitments, what it was buying, in which sizes and colors, and for how much, outside the system that tracked stock and money. Open orders, expected receipts and committed spend weren't visible in the books until the goods turned up at the warehouse. For a retailer, that's the difference between planning a season and reacting to it.
2. Two systems meant two versions of inventory
The retailer ran a common pairing. Fishbowl is sold as a way to get control of inventory without replacing QuickBooks: it handles stock and purchasing, and passes the accounting entries to QuickBooks, which keeps the general ledger. Fishbowl has no ledger of its own, so every receipt, transfer, adjustment and cost update has to sync across before it reaches the books.
That holds up while the business is small. It weakens as styles, sizes and locations multiply, and each failed sync, duplicate item or mapping error has to be found and fixed by hand. Fishbowl's own guidance says that past about 500 SKUs, businesses spend more time working around QuickBooks than in it. A retailer carrying every style in several sizes and colors passes that point quickly.
| Area | Before | After |
|---|---|---|
| Vendor orders | Spreadsheets, outside the system | Business Central purchase orders, entered in a size and color grid |
| Inventory | Fishbowl, synced to QuickBooks | Business Central, in the same database as the ledger |
| General ledger | QuickBooks | Business Central |
| Stock by location | Split across two systems | Central warehouse, in transit and every store, in one place |
| Item structure | No size and color ordering | Size and color variants on every style |
| Point of sale | In-house system | Same in-house system, integrated with Business Central |
| Servers and upgrades | Managed by the retailer | None: Business Central online, run by Microsoft |
3. One system, built around how the stock actually moves
Business Central keeps the general ledger and the inventory in one database, so there is no sync to break and no second inventory to reconcile. Multiple locations, transfer orders and item variants are standard. Cateran's work was making those features match the way the business moved goods:
- A central warehouse and transfers. Stock is received into the central warehouse and moved out to the stores on transfer orders. The business can see what's on hand at the warehouse, in transit, and on each store's shelves.
- Size and color variants. Each style is one item with variants for every size and color it comes in, so stock is tracked down to a single size and color at every location.
- Vendor orders in a grid. Standard Business Central has no size and color grid for order entry, so Cateran added a third-party Business Central extension that provides one. Buyers enter a style once and fill in quantities across the grid, the way they already thought about the order. The spreadsheets were retired, and open orders became visible before the goods arrived.
- The homegrown point of sale. The retailer ran its own in-house point of sale, so there was no off-the-shelf connector to buy. Cateran built a custom integration between it and Business Central.
4. Count first, warehouse second, stores last
The order of the go-live mattered as much as the configuration.
Count before you migrate. All the data in QuickBooks and Fishbowl came across to Business Central. Inventory was handled differently. Two systems that had been syncing for years didn't fully agree, and loading their numbers as they were would have carried the errors into the new system. So before the import, the company did a complete physical count to true up inventory. Business Central started with quantities that matched the shelves, by size and color, at every location.
Warehouse first. The central warehouse and inventory management went live on Business Central five months after the project started. Every store depends on the warehouse, so it had to be right before anything else moved.
Stores a few at a time. Over the next four months, the stores were brought onto Business Central in small groups. Each one went live against a warehouse that was already working and stock that was already accurate. Any problem found at one group was fixed before the next group went live, and the rest of the chain kept trading normally.
| Role | Responsibility |
|---|---|
| Lead architect | End-to-end design across Business Central and the point of sale, and the warehouse and inventory setup |
| Functional consultant | Setting up Business Central around the retailer's processes, from purchasing to store transfers |
| Data migration specialist | Moving all the data out of QuickBooks and Fishbowl, and loading the counted inventory |
5. The result: one system from vendor order to store shelf
- Warehouse and inventory live in 5 months, and every store live 4 months later, about 9 months in total
- Spreadsheet ordering retired: vendor orders raised in Business Central, by style, size and color
- One system of record for finance, inventory and purchasing, replacing QuickBooks and Fishbowl
- Clean opening stock: all data migrated, with inventory trued up by a full physical count before the import
- Stock visible by size and color at the central warehouse, in transit and in every store
- No servers to run: Business Central online, with Microsoft handling the infrastructure and upgrades
What finance leaders can take from this
- Look for the spreadsheets. When buyers or planners work outside the system, the biggest commitments in the business aren't in the books. That's usually the clearest sign you've outgrown your software.
- Inventory belongs in the ERP, not next to it. When stock lives in a separate app, the inventory number on the balance sheet is only as good as the last sync.
- Count before you migrate. Inventory that has been syncing between two systems rarely matches the shelves. A full count before the import means the new system starts with numbers people trust.
- Go live where the stock starts. Every store depends on the warehouse. Get it right first, then roll the stores out in small groups so problems stay small.
- A homegrown point of sale isn't a reason to stay put. A custom system can be integrated. The work is agreeing what data moves, in which direction, and how often.
Five questions to ask before you leave QuickBooks and an inventory add-on
- Are your buyers placing vendor orders in spreadsheets because your system can't handle sizes and colors?
- How much time does your team spend each month reconciling inventory to the books?
- Do you trust your on-hand numbers enough to load them into a new system, or do you need a count first?
- Could you open another store without adding finance or inventory headcount?
- Who will own the point of sale integration after go-live?
Client details are withheld at Cateran's discretion. QuickBooks is a trademark of Intuit Inc. Fishbowl is a trademark of its owner.
