Manage products, variants, and stock

A spare-parts dealer with roughly four thousand SKUs across a dozen vehicle brands has been running the business off three separate spreadsheets — one for stock, one for prices, one that somebody updates when a part actually sells — and the three have drifted apart for months. Nobody can say with confidence what's in stock without physically checking the shelf.

The product catalogue manager is built for exactly that scale of mess. Every product goes in once, with its own photos, description, price, and variants — like size, colour, or in this case a fitment detail — and stock is tracked per variant rather than per product, so a part that comes in three sizes shows three separate counts instead of one number that means nothing specific. A bulk import from a spreadsheet handles the dealer's existing four thousand lines in one pass rather than typed by hand.

The catalogue manager tracks what it's told, so its accuracy depends on how stock moves through the business day to day. A dealer who sells the same parts across a physical counter or a marketplace listing has stock changing in places the catalogue can't see unless that channel is also connected and kept in sync — without it, the system has no reservation logic for a sale happening elsewhere, and overselling a variant that looks available online but was just sold at the counter is a real, ongoing risk for any multi-channel seller.

Bulk import at genuine scale — four thousand SKUs and beyond — is where spreadsheet quality matters as much as the import tool itself. A large file with inconsistent formatting, missing fields, or duplicate SKU codes can cause the import to time out partway or complete with rows silently skipped rather than imported cleanly. Cleaning the source spreadsheet before uploading — consistent columns, no blank fields, no repeated SKU codes — reduces the chance of a partial import leaving the dealer unsure which products made it in.

Duplicate SKUs deserve caution beyond the import step. If two products share an identical SKU code, the system has to resolve the collision, and one product can end up overwritten or merged incorrectly with the other. A dealer converting from a spreadsheet system where SKU discipline was loose should expect to spend real time deduplicating codes before the first import, since fixing a collision after four thousand products are live is harder than catching it first.