Push your whole catalogue to Linnworks — and a place that tells you what needs attention

Bulk catalogue push, running in the background

Sending an existing catalogue to Linnworks one product at a time was never going to work. There's now a bulk push that runs on the server — start it and walk away. You can cap a run if you'd rather move in batches, and scope one to products created since a given date, which is what you want after the first full push.

Actions: what needs you, in one place

A new Actions surface, with an indicator in the navigation and a widget on the dashboard. Rather than discovering problems by opening products at random, the things that need a decision come to you.

Orphan detection

Fulify now tracks sync state per destination and spots orphans — a stock item sitting in Linnworks with no matching product in Fulify, usually left by a SKU change or an earlier tool. Each one is named and linked back to the product it belongs with, so you can see what it is rather than just a count.

Fixes worth calling out

Several of these were found by testing against the live Linnworks API rather than its documentation, and every one of them failed quietly — the sync reported success while doing the wrong thing.

• Parent links were writing an empty name. The parent-child relationship was created with nothing in it. Now written as Parent ID, correctly.
• Lookups were reading only the first page, so a product past the first page of results looked like it wasn't in Linnworks and was created a second time.
• Stale mappings survived a re-credentialling and pointed at items that no longer existed.
• "No SKU" is now reported up front, rather than only after a sync has failed. A product with no SKU can't sync anywhere — you should hear that when you look at it, not after you've tried.
• Contrast, an admin gate, a miscount and a polling loop, all from a quality audit.