Linnworks, a full audit trail, and one master switch for sync

A big release. Fulify now talks to your warehouse, remembers who changed what, and gives you a single switch that decides whether a product leaves Fulify at all.

Linnworks: your warehouse gets products the moment they exist

Fulify now syncs products straight into Linnworks as stock items. Matching is on SKU — create-or-update, so it never duplicates — and a variant group of ten becomes ten stock items, the way Linnworks expects.

It runs inside Fulify. No connector to buy, no middleware to babysit.

One deliberate omission worth knowing: retail price is not sent. A Linnworks stock item has no retail-price field — pricing there is per-channel. Fulify sends content, identifiers, weight and dimensions, and leaves price alone rather than writing it into PurchasePrice, which is a cost field and would quietly corrupt your margins.

One master switch: Sync

Sync is now the single gate on a product. Off means it stays in Fulify and reaches no channel at all — however the sync is triggered, whether that's you pressing a button, a scheduled publish, a save, or a per-channel resync.

Show on Storefront stays as the finer control for products that are syncing.

The practical use: get a product into the warehouse and onto your team's screens long before marketing has signed off the copy.

Every change, recorded

Fulify now keeps a field-level history of every product change — what changed, what it was before, what it became, who did it, and when. Open History in the product editor for a readable timeline.

It covers all three ways data gets into Fulify, and tells them apart: a person editing in the app, a CSV import, and a write through the API. When a price looks wrong three weeks later, the answer is in the record rather than in anyone's memory.

Installable integrations

Integrations now have a proper install / uninstall section rather than being configured in scattered places, so connecting Linnworks is a deliberate act with a clear on and off.

Aviation parts traceability (proof of concept)

For customers in aviation: products can now carry structured airworthiness data — part number, serial or batch-lot number, condition, traceability source — plus a linked certificate document, pushed to Shopify as aviation.* metafields for display on the product page.

To be clear about scope: this is a structured-data and document layer. Fulify records and moves what you tell it. It is not the airworthiness judge.

Typography and polish

Fulify moved to a self-hosted font pipeline with proper typography tokens — faster loading, no third-party font requests, consistent type across every screen. Links, layering and contrast all got a pass at the same time.