✨ What this means for you:

• Shopify metafields and Magento custom product attributes are discovered automatically — no schema setup, no field list to maintain.
• Every attribute shows how many of your products carry it and up to three real sample values, so you can tell a genuine attribute from an app's leftovers before you map it.
• Map an attribute to any SKU product field — a catalog attribute, the title, a weight, a price tier — and the channel's value lands there.
• Need a catalog attribute that doesn't exist yet? Type the name, press Enter, and SKU.io creates it for you.
• Map at creation time to fill new products from the channel, or in Content Sync to keep them current and get flagged when the channel edits them.
• Clean values on the way in — strip a channel-specific SKU prefix, trim a trailing size code, join two fields together — without touching them afterwards.
• Nothing is mapped by default. An attribute you don't map is ignored entirely.

Two places to map, and they do different jobs​

This is the part worth getting right up front, because the two surfaces look similar and behave very differently.

Field Mappings decides what fills a SKU product the first time it's created from a channel listing. It runs once per product, at creation, and then it's done. It's the widest of the two — it can reach almost any SKU field.

Channel Attributes, inside Content Sync, decides what keeps flowing after the product exists. Those mappings are applied on every sync, and the ones that land on fields Content Sync governs are also compared against your catalog, so a merchandiser editing the material in Shopify raises a reviewable change instead of a silent divergence.

Most teams want both: Field Mappings to get a new product populated, Channel Attributes to keep it honest.

Discovering what your channel actually sends​

Open a channel's Products page and select Field Mappings, and the channel's own vocabulary is already there beside its standard fields — grouped as Metafields on Shopify and Custom Attributes on Magento, each labelled with how many of your products carry it.

Shopify metafields read the way you named them: custom.care_instructions shows as Custom: Care Instructions, shopify.material as Shopify: Material. Magento attribute codes are title-cased from the code itself — country_of_manufacture as Country Of Manufacture. Filter to Unmapped after a first sync and you're looking at exactly what the channel is sending you that SKU.io is currently throwing away — which is usually where the useful merchandising data has been hiding.

None of this comes from asking the channel for a schema. SKU.io builds the list from the products it has already synced, which means what you see is what your store genuinely uses, not every field the platform theoretically supports.

Clean the value on its way in​

Channel data rarely arrives in exactly the shape your catalog wants. A transform reshapes it during import, so you're not fixing the same thing by hand every time a product is created.

Pick a mapped row, select Add Transform, and choose what to do: Remove Text deletes every occurrence of a string, Find & Replace swaps one for another, Remove from Beginning and Remove from End trim a fixed number of characters, and Append Field joins another channel field on with a separator you choose. Stack more than one and they run in order. Transforms are available on Amazon, BigCommerce, eBay, Shopify, TikTok Shop, Walmart and WooCommerce.

Keep them current, and catch the edits​

The other half lives at the bottom of a channel's Content Sync settings tab. Same vocabulary, different job: these mappings run on every sync.

Each row tells you what you need to decide with: Coverage — how many of your synced products carry it, so an attribute on 12 of 12 is obviously worth mapping and one on 2 probably isn't. Sample values — up to three real values pulled from your own listings, so you see what you'd be importing before you commit. Then pick a target in Maps to and switch the row Active.

Targets that Content Sync governs — Basic Info, Physical, and Product Attributes — are written on sync and compared, so a change on the channel side shows up in the Content Sync inbox like any other drift, with the before and after side by side. Pricing and supplier targets are written but never compared; the panel labels them written, not compared so you're never guessing which you picked.

Magento stores get the same treatment for their custom product attributes: point Manufacturer at Brand, material at a Material catalog attribute, and leave the shipping-compliance codes you don't maintain in SKU.io unmapped.

One thing to know: on Magento 2, custom attributes are available in Field Mappings at product creation but not in Channel Attributes, so a Magento 2 custom attribute can fill a SKU field when the product is created but can't be watched for drift afterwards. Shopify metafields and Magento 1 custom attributes can be. The eight governed content fields sync normally on Magento 2 either way.

Where to find it​

Creation-time mapping: Apps & Integrations → your channel → Products → Field Mappings. Ongoing mapping and drift detection: Apps & Integrations → your channel → Settings → Content Sync → Channel Attributes. Mappings are saved per connection, so two Shopify stores can map differently.

Full guides:

• Map channel fields to SKU products — everything that happens at product creation, including transforms and the per-channel differences.
• Review and apply channel content changes — Channel Attributes, drift detection, and the rest of Content Sync.

✨ What this means for you:

• Every channel-side content change lands in one inbox, broken out field by field — not "this product changed" but "the weight changed from 5.4 kg to 5600 g".
• You set the source of truth per field group: your catalog wins, the channel wins, or two-way.
• Nothing touches your catalog until you look at it. Review the before/after, then Apply or Ignore.
• A channel-side bulk edit that hit 40 listings is one row and one Approve all click, not 40 reviews.
• Let safe fields like weight and images apply automatically while the product title waits for a human.
• When both sides changed the same field, you get an explicit choice — never a silent overwrite.
• One listing needs different rules than its channel? Override it in place, without touching the channel.
• Every applied change is reversible, and the full history is filterable, comparable, and exportable.
• Need the differences that were already there before you switched it on? Run a full comparison on demand.
• Optionally block publishing to a channel until the content that channel requires is actually filled in.

One inbox for every content change​

PIM → Content Sync is the queue. Cards across the top count what's waiting — Pending, Conflicts, Errors, and how many listings are affected — and the sidebar carries a badge so you notice new drift without going looking for it.

Each row is a single changed field, with the old value, the new value, which channel it came from, and when it was detected. Filter by status, field group, channel, riskiness, or source; search by SKU, product name, listing title, or the change ID itself. The field that carries the most marketing weight — the product Title — is flagged risky, so it can't be waved through in a bulk action by accident.

Approve a whole templated change in one click​

Channel-side edits are rarely one-offs. A supplier re-weighs a range, an ops teammate reformats every title, a photographer re-shoots a category — and forty listings change the same field on the same afternoon. Grouping turns that into a single decision.

Set Group by to Field (the default) and each bucket becomes one row: "Weight changed", "5 changes across 5 listings", and an Approve all button that applies the whole batch as a background job you can watch in the job tray. Click the bucket itself to focus the feed on just those changes.

Risky fields stay out of it by design. Group by Field and the Approve all button on the Title changed bucket is disabled outright — "Risky fields have to be reviewed listing by listing." Group by Field group and Approve all quietly skips the risky fields inside the group and applies the rest.

Review the diff before you accept it​

Click any row and the review drawer opens with the catalog value on the left and the incoming channel value on the right — rendered for the kind of field it is, so you're reading the change and not hunting for it.

Titles and brands highlight the individual words that were added and removed, so a one-word retitle doesn't read as a full rewrite — and if only spacing or markup moved, it says so instead of showing you a diff. Image changes come as thumbnail strips with the removals and additions called out. Attributes list only the keys that actually changed. Weights and dimensions carry their units, and applying converts them: a channel that says 1650 g writes 1.65 kg into a catalog that tracks kilograms.

Apply or Ignore field by field, or clear the whole listing at once: Apply all safe takes the low-risk changes and leaves the flagged ones alone, Apply ALL takes everything including the risky fields, and Ignore all dismisses the lot. An ignored change stays dismissed until the channel value genuinely changes again — the same edit won't resurface on every re-check. Reconcile now re-checks that listing against the channel on the spot.

You decide who owns each field​

Content sync is off by default on every channel, and turning it on doesn't change a single value — it starts watching. Open Apps & Integrations → your channel → Settings → Content Sync.

Eight fields are governed, grouped so you can set ownership once: Identity (Barcode, MPN), Descriptive (Title, Brand, Attributes), Media (Images), and Physical (Weight, Dimensions). For each group, pick who owns it — Catalog, Channel, or Two-way — and whether inbound changes auto-apply or queue for review. Need one exception inside a group? Open Field overrides and set that single field differently. You can also choose how often listings are re-checked as a backstop to real-time webhooks, and let SKU.io fill genuinely empty catalog fields from the channel automatically — filling a gap is not the same risk as overwriting curated copy.

One thing worth knowing: switching content sync on baselines the listing content as it stands right now. Differences that already existed aren't dredged up retroactively — only changes made from that point on are flagged as drift. You're starting from a clean inbox, not inheriting years of history.

When you do want the whole picture​

That clean-inbox default is the right one day to day, but it has a corollary: a difference that was already there when you switched content sync on stays invisible, because the channel never moved. If you imported your products from Shopify and only started governing attributes or dimensions later, a normal re-check has nothing to report — it's comparing against a baseline that already contained the mismatch.

Full comparison is the answer. Open the arrow beside Reconcile and pick it, and SKU.io ignores the baseline entirely: it diffs every governed field against your catalog as things stand right now, whether or not the channel content has changed since the last check. Pre-existing gaps surface as ordinary pending changes you can review, apply, or bulk-approve exactly like any other drift.

It's there on both scopes — Reconcile now → Full comparison in the review drawer for a single listing, and Reconcile → Full comparison in the inbox for a channel or the whole tenant. Because it reports every difference rather than only the new ones, scope it with the channel filter when you're backfilling; a tenant-wide pass can raise a lot at once, and the confirmation says so before it starts.

…and one listing can disagree with its channel​

Channel settings are the default, not a straitjacket. When a single SKU needs different treatment — one hero product whose title you never want touched — expand Customize for this listing in the review drawer and set ownership or auto-apply for that listing alone. A chip at the top tells you where it stands: "Inherited from Amazon defaults" or "3 customizations on this listing", and Reset to channel defaults hands it back.

Overrides are sparse, not snapshots. Only what you explicitly change is stored, so everything you leave alone keeps tracking the channel — later changes to the channel's defaults still flow through.

When both sides changed​

Set a field to two-way and eventually both sides will edit it between syncs. SKU.io refuses to guess.

The field is marked Conflict and held until you choose: Keep mine keeps your catalog value and dismisses the channel edit, Take theirs overwrites with the channel value, and Keep both takes the channel value now while preserving your version for the next outbound push. Whichever you pick, the other value is recorded rather than discarded.

Nothing is one-way​

Change history at the bottom of the review drawer is the full audit trail for a listing's content — applied, auto-applied, ignored, superseded, conflicted, errored, and rolled-back entries, each with who resolved it and when. Filter it by field, status, who detected it, who resolved it, and a date range.

It reads outcomes, not attempts: a change that never wrote to your catalog shows its before → after struck through, so an ignored suggestion can't be mistaken for an applied one. Tick two entries on the same field and Compare versions shows the value that field held after each — read-only, so nothing you do while comparing can touch the catalog. Anything that did write gets a Roll back button that restores the value it replaced, and the rollback is itself recorded, with a button that reads Undo rollback. Export the filtered history as CSV when someone needs it in a spreadsheet.

Stop incomplete products from shipping to a channel​

The same content rules can work in the other direction. Turn on Block publishing when required content is missing at the bottom of a channel's Content Sync settings and pick what that channel insists on — Barcode, Images, Dimensions, whatever it needs.

From then on, publishing a listing to that channel checks the catalog product first, and if anything required is empty the publish job fails naming the exact gap: "Blocked by the content governance gate — this product is missing Barcode, Images." The gate is deliberately outbound only. Inbound content is never blocked, because inbound content is how an incomplete product gets filled in.

Where to find it​

The inbox lives at PIM → Content Sync — beside the other surfaces that own product content. Turn it on per channel from Apps & Integrations → your channel → Settings → Content Sync, where you'll also find field ownership, auto-apply, and the governance gate.

Full guide (with a 1:40 video walkthrough): Review channel content changes

✨ What this means for you:

• Orders for an out-of-stock SKU stop stalling when an equivalent is on the shelf — swap one line in a click, or bulk Swap & Release the backlog.
• A Swap resolvable tab on Sales Orders counts every stalled order a substitution could release right now, so the opportunity is never invisible.
• Customer documents stay honest: the invoice and packing slip keep the ordered SKU; the pick list shows the substitute with the original in brackets so pickers grab the right part.
• Substitutes can count toward the availability you publish to your sales channels — so a listing backed by interchangeable stock stays buyable instead of showing sold out.
• Demand and profit follow the SKU that actually ships, so replenishment reorders the right item instead of the alias.
• Manage rules anywhere: per-product on a Substitutes tab, or across your whole catalog on a Substitutions page with Excel import and export.

Set the rules once, per product pair​

Open a product's Substitutes tab and add the equivalent you stock. Each rule has a mode: Manual only (a person applies it from the order line), Only when out of stock (swaps automatically when the ordered product can't cover the line), or Always (every order swaps — perfect for part numbers you list for search but never stock). You can also allow swaps when the substitute is itself out of stock, and choose whether its stock counts toward the original's published availability.

Spot the stalled orders a swap would fix​

The Sales Orders page gains a Swap resolvable tab with a live count of stalled orders that a substitution could release right now. Click it and you're looking at exactly those orders — nothing else.

On any stalled order, lines with a matching rule show a Swap available chip. The menu lists each substitute with its live availability, the rule's mode and notes, and marks the ones that fully resolve the shortfall — one click swaps the line and allocates stock from the substitute.

Release a whole backlog — with a preview first​

Select the stalled orders and choose Swap & Release. Before anything runs, a confirmation shows precisely what will happen: each order's planned swaps — ordered SKU → substitute SKU with quantity and rule mode — plus any orders that would be skipped and why. Confirm, and a background job applies the swaps and sends the orders to fulfillment while you watch the resolvable count drop to zero.

Where to find it​

Turn the feature on under Settings → Products → Product Substitutions. Manage rules on any product's Substitutes tab or the Substitutions page under PIM, and work the backlog from Orders → Sales Orders → Swap resolvable.

Full guide: Substitute an out-of-stock product on a sales order

✨ What this means for you:

• No middleware. Connect Airtable directly from SKU.io — no Zapier, no Make, no per-task billing, no third vendor to blame when a sync breaks.
• Both directions. Push SKU.io data into Airtable, and let a narrow, safe set of Airtable edits flow back into your catalog for review.
• A base in one click. Let SKU.io provision a ready-made "Ops Hub" base — the right tables and field types, pre-mapped and backfilled — so you're synced in minutes.
• On your schedule. Sync every 15 minutes, hourly, daily, on demand, or in real time as records change.
• Safe by design. Only fields you map are written, and inbound edits can never touch order status, inventory, costs, or pricing.

Connect your account — and see everything in one place​

Connecting is a single OAuth handshake: open Apps & Integrations → Airtable, select Connect Airtable, and grant access in the Airtable window. Once connected, a dashboard shows your account, connection status, the exact scopes you granted, and your monthly Airtable API usage — so you always know the sync is healthy.

Map any dataset — and sync it your way​

Each row on the Datasets tab ties one SKU.io dataset to one Airtable table. A guided wizard walks you through the dataset, the destination base and table, the field mapping, and the options — sync direction, schedule, real-time push, and how deletions are handled. Seven datasets are available; Products, Sales Orders, and Suppliers can sync two ways.

Once a dataset is mapped, push the latest data any time with Sync now, or let it run on the schedule you chose. SKU.io matches records by a stable key, so repeat syncs update the same Airtable rows instead of creating duplicates.

Let Airtable enrich your catalog — safely​

Airtable is a great place for content and planning teams to work, so the integration lets a whitelisted set of edits flow back into SKU.io. When someone changes a safe field in Airtable, the change lands in an Inbound review queue — showing the record it affects, the old and new values, and a status — so you approve it before it updates your catalog. Operational fields like order status, inventory, costs, and pricing are never writable from Airtable.

Where to find it​

Open Apps & Integrations → Airtable and select Connect Airtable to get started. For step-by-step guides and short walkthrough videos — connecting, mapping and syncing, reviewing inbound changes, and the full field reference — see the Airtable integration documentation.

✨ What this means for you:

• A dashboard per job. Build an Overview, a Sales board, an Operations board — as many as you need — and flip between them instantly.
• 100+ widgets, one picker. Browse by category or search, and drop in exactly the metrics you care about.
• See it before you add it. A live preview renders each widget with your data, so you never add a card and hope.
• Arrange it your way. Drag widgets to reorder, resize them from a third of the row up to full width, and reorder your dashboards themselves.
• Works on your phone. Your dashboards follow you to mobile in a clean single-column view.

Add exactly the widgets you want​

Click Customize, then Add widget, and the widget picker opens. On the left, widgets are grouped by area — Sales & Orders, Inventory & Stock, Financials & Profitability, Forecasting & Demand, and more — or you can search all 100+ at once. Pick a card and the panel on the right shows a live preview built from your real data, so you know precisely what you're getting before it goes on the board.

Add a widget and it drops onto your dashboard and scrolls into view. In edit mode you can drag any widget to reorder it, set its width, or remove it — then Save (or just press ⌘/Ctrl+S). Changed your mind? Cancel (or Esc) backs out, and you'll be asked before anything is discarded.

Keep several dashboards and switch in a click​

One board rarely fits every role. Create as many named dashboards as you like and switch between them from the tabs at the top — each remembers its own set of widgets and layout. Rename them, set a default that opens when you sign in, drag the tabs to reorder them, and delete the ones you no longer need.

Take it with you​

Your dashboards aren't just a desktop thing. On a phone, the same board you built stacks into a clean single column, and the tab switcher comes along so you can jump between your Overview, Sales and Operations views on the go.

Where to find it​

It's your home screen. Open Dashboard from the main menu, then click Customize in the top-right to add, arrange and resize widgets, and use the tabs beneath the title to create and switch between dashboards.

Full guide: Customize your dashboard

✨ What this means for you:

• Choose how each baseline is calculated — a flat average, a recency-weighted average, or a damped trend that projects recent growth forward without overshooting.
• A growing product is planned closer to its current pace, not a stale average; a declining one winds down instead of over-ordering.
• Every recommendation now shows its decomposition — base velocity, the trend applied, and the final daily rate — so you can see exactly why the number moved.
• One-off spikes — a past promotion, a data glitch — can be excluded from the baseline automatically, so they don't inflate your everyday demand.
• Turn a past promotion into a reusable lift: measure it once, and it re-applies at today's volume — a promo that lifted you 2.5× still lifts 2.5× after you've doubled.
• Promo windows are suggested for you from detected sales spikes, so you confirm a date range instead of typing one.
• The full decomposition downloads with your export, alongside the confidence and rationale you already get.

Pick how your baseline is calculated​

Open Inventory → Demand Planning and you'll find a new Baseline method control in the forecast configuration. Leave it on Flat mean for the classic behavior, or switch to Recency-weighted to lean on your most recent sales, or Damped trend to project a product's recent growth forward. Choosing Damped trend reveals two dials — Trend damping, which controls how strongly the trend carries forward, and a Max growth cap so a short-term surge can't run away with your order. There's also an Exclude detected anomalies from baseline option that keeps one-off spikes out of your everyday demand.

See the number build, step by step​

Build the forecast and each line's daily rate now reflects its trend — a fast-growing product reads noticeably higher than its flat average, a fading one reads lower. Click the calculator icon on any row and the calculation detail opens with a new Baseline decomposition: it shows the base velocity the product would sell at flat, the trend that was applied (and whether the growth cap kicked in), and the final baseline the order is built from — so the reason behind every recommendation is right there, not hidden in an average.

Re-use a promotion — and let it grow with you​

Ran a sale last year and want to plan for it again? Open Promo Windows, mark the promotion's dates, and measure the lift it produced against your real sales history. From there you can apply that lift to your forecast — and because it's stored as a multiplier rather than a fixed number of units, it re-applies at today's volume automatically. A promotion that lifted demand 2.5× still lifts it 2.5× after your baseline has doubled, with nothing to recalculate. To make setup easier, Suggest from spikes scans your sales history and proposes the promotion's date range for you.

Where to find it​

• Choose your baseline: open Inventory → Demand Planning, and in the Configuration panel set the Baseline method (and, for Damped trend, the damping and growth cap).
• See the decomposition: after you Build Forecast, click the calculator icon on any line and read the Baseline decomposition at the top of the calculation detail.
• Re-use a promotion: open Promo Windows from the forecast results, create or Suggest a window, Measure lift, then Apply it — it lands as a demand modifier ready to build.
• Take it with you: click Export and keep Include calculation details switched on to download the full baseline and promo breakdown for every line.

✨ What this means for you:

• Add an Advanced lead times override on any supplier — a specific number of days for a specific warehouse — right on its Purchasing settings.
• Warehouses you don't override simply inherit the supplier's default lead time, so you only configure the exceptions.
• Demand planning and reorder suggestions use the lead time for the destination warehouse you're forecasting — so multi-region and multi-warehouse buys stop sharing one blended (and usually wrong) number.
• Every forecast tells you which lead time it used — the supplier's default, a per-warehouse override, or a measured actual from your own receiving history — so the number is always traceable.

Set lead times per warehouse, right on the supplier​

Open a supplier and go to Purchasing Defaults. The Lead Time field is the supplier's default — used everywhere unless you say otherwise. Just below it, the new Advanced lead times section lets you add an override: pick a warehouse, enter the number of days, and add another for each exception you have. In the example below, this supplier normally takes 14 days, but reaches the London Warehouse in 45.

Only configure the exceptions​

There's no need to fill in a row for every warehouse. The overrides you set are listed clearly on the supplier, and every other location quietly falls back to the default lead time above — so a vendor that's slower to just one region takes a single line to configure, not a table full of duplicates.

The forecast uses the right one — and shows you which​

When you build a demand-planning forecast with a destination warehouse selected, SKU.io resolves the lead time for that warehouse: a per-warehouse override wins first, then a measured actual learned from your own purchase-order history, then the supplier's default. Because each destination now plans on its own real lead time, a US buy and a UK buy for the same vendor no longer share one figure — and the Lead column on every line tells you exactly which source drove the number, so a longer overseas lead time is never a mystery.

Where to find it​

• Set the overrides: open Contacts → Suppliers, choose a supplier, then Settings → Purchasing Defaults, and add rows under Advanced lead times.
• See it applied: open Inventory → Demand Planning, build a forecast with a destination warehouse selected, and check the Lead column — hover it to see which lead time the forecast used for that location.

✨ What this means for you:

• Every forecast line shows a confidence tier — High, Medium, Low, or New — so you can see at a glance which recommendations to trust and which to review.
• A likely range sits under each quantity (for example, 158–194), so you see the uncertainty, not just a single point number.
• Brand-new and thin-history products are flagged New instead of quietly emitting a confident-looking figure you can't rely on.
• The calculation detail explains the score — the drivers behind it, plain-English reasons, and a suggested fix when confidence is low.
• A one-line rationale puts the whole calculation in words anyone can read — no formula-decoding required.
• The export now matches what you see on screen — confidence, the likely range, the input sources, and the rationale all download to CSV or Excel for a complete, defensible audit trail.

See which numbers to trust — at a glance​

Build a forecast and each line now has a Conf column. A colored chip tells you the confidence tier for that recommendation, and just below the recommended quantity you'll see the likely range the forecast expects demand to fall within. A steady, well-established product reads Medium or High; an intermittent seller with sparse history reads Low; a product with almost no sales in the window reads New — so a thin-data guess never masquerades as a sure thing.

Understand the why — and what to do about it​

Open any line's calculation detail and the new Confidence section shows exactly how the score was reached. Four drivers are laid out plainly — how much sales history the product has, how densely it actually sold, how variable demand is day to day, and how recently it last sold — each marked good or flagged. Below that, a short Why explains the tier in one or two sentences, and Suggested fixes point you at the next step (for example, link a predecessor product or extend the sales window). The likely range is stated as a service level, and a plain-language rationale summarizes the whole thing: "Ordering 176: 31 days of history at 4/day, 14-day lead time… Confidence Medium… Likely range 158–194 at 90% service level."

Export the whole story​

When you export the forecast, a new Detail section lets you choose exactly how much of the calculation to include. Keep calculation details and confidence & rationale switched on and the download carries everything you see in the app — the confidence tier and score, the likely range, the input sources, and the plain-language rationale for every line. The file you hand to finance is now a complete, self-explanatory record of how each reorder number was reached.

Where to find it​

• See it on your forecast: open Inventory → Demand Planning, choose your suppliers, and click Build Forecast — the Conf column and the likely-range figures appear on every line.
• Dig into a number: click the calculator icon on any row to open the calculation detail, then read the Confidence section, the drivers, and the rationale.
• Take it with you: click Export (top right) and, under Detail, keep Include confidence & rationale switched on before downloading your CSV or Excel file.

✨ What this means for you:

• A full timeline of every recipe change — every version of a bundle or kit's recipe, with what changed, when, and who made it.
• See the recipe as of any date — pick a date and SKU.io shows exactly what the product contained then.
• Editing no longer rewrites the past — a change applies from today forward, so last quarter's records stay exactly as they were.
• Schedule a change ahead of time — set a new recipe to take effect on a future date; today's recipe stays live until then, then switches over automatically.
• Correct the past when you need to — fix a recipe that was recorded wrong for a stretch of time, clearly flagged as a correction, and bring the affected orders back in line.

A full history of every recipe​

Every bundle and kit now has a Composition tab that shows its recipe as a timeline. Each entry is a dated version — active now, superseded, scheduled for later, or a correction — with a plain-language note of what changed and who made it. Alongside it, the Effective Recipe panel shows exactly what's in the product today. No more guessing whether the recipe you're looking at is the one that was in effect last season.

See the recipe as of any date​

Set the As of date and the Effective Recipe updates to show what the product contained on that day. A kit that ships with three components today might have had two last summer — and now that's a single click to confirm, not an archaeology project. Because the history is real, a recipe you edit today never changes what the product looked like on an earlier date.

Schedule a change ahead of time​

Planning a formulation update or a seasonal edition? Open New recipe change, adjust the components, and set the effective date in the future. SKU.io schedules it: the live recipe stays exactly as it is until that day arrives, then the new one takes over on its own. You can line up a change weeks ahead without it affecting anything you sell today.

Correct the past when you need to​

Sometimes a recipe was simply recorded wrong for a stretch of time. Set the effective date in the past and confirm, and SKU.io files it as a correction — changing only that window's history, and marking it clearly so the change is always attributable. For bundles, you can take it a step further: SKU.io lists every order placed in that window — with each one's status and the exact before → after for each component — so you can bring the affected orders in line with the corrected recipe.

Where to find it​

Open any bundle or kit product and select the Composition tab. Your product's current recipe is on the right; its full history is on the left; and New recipe change lets you edit it now, schedule it for later, or correct it in the past.

✨ What this means for you:

• A Drop-ship Status checklist tells you at a glance whether a product will drop-ship — and, if not, exactly what's missing — so you never wonder why an order backordered.
• Out-of-stock orders for eligible drop-ship products route to your supplier automatically — no manual warehouse assignment.
• The supplier purchase order is created and sent for you, either the moment the order is placed or batched at times you choose.
• You can see whether a drop-ship PO has been sent to the supplier right on the order — and the fulfillment step reads "Mark Shipped," so it's clear the supplier, not your warehouse, is doing the shipping.
• One clear place to configure drop-ship on a supplier, with a per-supplier stock setting instead of a hidden fixed number.

See exactly why an order will — or won't — drop-ship​

Drop-shipping is deliberately explicit: an order only routes to a supplier when the product, the supplier link, the supplier's warehouse and its stock feed are all in place, so nothing is ever sent to a supplier by accident. The new Drop-ship Status panel makes those requirements legible in one spot. Open a supplier's product and it shows an Eligible / Not eligible badge and a checklist of every requirement, each ticked green or flagged, with anything missing called out so you know precisely what to fix.

Route out-of-stock orders to your supplier — automatically​

Turn on Enable drop-ship auto-routing and your drop-ship supplier becomes a stop in your warehouse priority list — drag it wherever it belongs. When an order can't be filled from your own stock, SKU.io routes the eligible lines to that supplier instead of backordering them against your primary warehouse.

You stay in control: a line only ever drop-ships when the product, the supplier, and the supplier's warehouse are all opted in — so nothing gets sent to a supplier by accident.

Set up drop-ship in one place — and choose when POs go out​

Every supplier now has a dedicated Dropship section. Switch on Automate Dropship Fulfillment to create the purchase order automatically when an order routes to that supplier, and Automate Dropship PO Submission to send it to them.

You decide the timing. Submit immediately sends each PO to the supplier the moment it's created. Batch on a schedule holds new POs and sends them together at the times you set — handy when a supplier prefers one consolidated order a day.

Always know where the order stands​

On an order's Fulfillment view, a drop-ship line clearly shows its supplier purchase order and whether it's been sent. Because the supplier is doing the shipping, the action reads Mark Shipped rather than a generic "fulfill" — so it's obvious what's happening and who's shipping.

And if a supplier is missing a purchase-order email, SKU.io flags it up front — on the supplier and on the PO — instead of silently failing to send, so a drop-ship order never sits waiting on a notification that was never going to arrive.

Where to find it​

• Check what's needed (start here): open the supplier's product under Contacts → Suppliers → (your supplier) → Products — the Drop-ship Status panel shows the Eligible / Not eligible badge and ticks off each requirement, so you can see at a glance what's set and what's still missing.
• Mark a product drop-shippable for a supplier: on that same supplier-product page, set the link's Drop-ship / Always option (this is the master switch — the product's own drop-ship flag and the supplier warehouse must also be enabled, and the status panel tells you if either isn't).
• Turn on auto-routing: Settings → Fulfillment → Warehouses → Enable drop-ship auto-routing, then order your Warehouse Priority list.
• Configure a supplier's automation: Contacts → Suppliers → (your supplier) → Settings → Dropship — automate fulfillment, automate submission, and choose immediate vs. batched sending.
• Track an order: open any drop-ship sales order and switch to the Fulfillment tab.

✨ What this means for you:

• Opt in per product — enable serial tracking only where you need it, so the rest of your catalog stays simple.
• Capture a serial for every unit as you receive stock — type, scan, or paste in bulk, with automatic uniqueness checks.
• Choose the exact units at fulfillment — SKU.io suggests the oldest-received serials first and won't let you ship until every unit is confirmed.
• See serials on your documents — pick lists and packing slips list the exact units to grab, each with a check-off box.
• Trace any unit end to end — search by serial, follow its full Received → Shipped timeline, and quarantine a unit in one click when it has to come off the shelf.

Turn it on only where you need it​

Serial tracking is a two-step opt-in, so it never gets in the way of products that don't need it. First an admin flips the tenant-wide switch in Settings → Inventory → Inventory Tracking; then each product that should be serialized gets its own Track Serials toggle on its Serial & Lot Tracking tab. You also choose how serials are created — type or scan each one yourself, with SKU.io validating uniqueness for you.

Capture serials as stock comes in​

Once a product is serialized, receiving stock asks for the detail that matters. Add inventory as usual and a Serial Numbers field appears, keeping a running count against the quantity — "3 of 3" — so you can't commit a receipt that's missing a unit. Scan them one at a time, type them, or paste a whole list at once; each serial becomes a chip you can review and remove before you commit.

Pick the exact units when you fulfill​

When you ship a serialized product, SKU.io does the choosing for you — and lets you override. The fulfillment dialog suggests serials oldest-received-first and counts them against the quantity ("3 / 3"), so a serialized line can't ship a unit short. Need to send a specific one instead? Remove a suggestion and scan or type the serial you're actually pulling. The units you confirm are the ones recorded as shipped against the order — so the trail from receipt to customer is exact.

Serials on your pick lists and packing slips​

Your warehouse paperwork now carries the detail that matters. Pick lists and packing slips print the specific serials for each line — each with a check-off box — so whoever's packing the box grabs exactly the right units and can tick them off as they go. It happens automatically for serialized products; documents for everything else look exactly as they do today.

Trace every unit — and pull one when you need to​

Every serial has its own page with a full Received → Shipped timeline, linked back to the product, warehouse, and order it moved through — so a warranty claim, a recall, or a "where did this one go?" question is a single lookup, not an investigation. Browse or search the whole list from Inventory → Serial Numbers, filter by status, and when a unit has to come off the shelf — damage, inspection, a recall — quarantine it in one click to hold it out of stock, then release it back once it's cleared.

Where to find it​

Switch it on under Settings → Inventory → Inventory Tracking, then enable Track Serials on any product from its Serial & Lot Tracking tab. From there it flows on its own: every receipt captures serials, every fulfillment lets you choose them, and your pick lists and packing slips print them. Look up any unit anytime from Inventory → Serial Numbers. Lot and batch numbers work the same way for products that need expiry or batch traceability instead.

✨ What this means for you:

• Removing stock? See every order that will drop back to backorder — with the customer and quantity — before you confirm.
• Adding stock? See which backordered orders the new units can fill, and choose which ones get filled first.
• Never stuck when stock is already committed — you can send the affected orders to backorder, or even void the shipping label with the carrier (when it's still eligible) to free the units.
• A live On Hand / Available / Allocated readout on every adjustment, so you always know what's really free to move.

Removing stock? See exactly who it affects​

Pick a product and choose Decrease, and SKU.io shows an Allocation Demotion Preview: the specific orders whose stock you're about to reclaim, each with its customer and quantity, ordered so the least-urgent commitments are consumed first. Instead of discovering a backorder after the fact, you see it before you click — and you can dial the quantity down if the impact is more than you intended.

Adding stock? Choose which orders it fills​

Switch to Increase (or receive against a purchase order) and the same panel flips to an Allocation Release Preview: it shows the backordered orders your incoming units can unblock, each with a checkbox. Fill them all, or hand-pick which orders get the stock first — you're in control of where the new inventory lands, right at the moment you add it.

Already spoken for? You still have options — not a dead end​

Sometimes the stock you're trying to remove is already allocated to orders, so a straight reduction isn't possible. Instead of a hard stop, SKU.io lays out your choices:

• Reserved-but-not-yet-shipped units can be sent straight back to backorder — you see exactly which sales orders are affected, and decide whether that trade-off is worth it.
• Units already on a printed shipping label are protected: rather than pulling stock out from under a shipment, SKU.io offers to void the label with the shipping provider — when the carrier still allows a cancellation — and return those units to stock. If a label isn't eligible to be voided, you'll be told plainly, so nothing is taken by force and no order gets double-shipped.

Either way, when the stock isn't freely available you always have a clear, deliberate path — backorder the order, or void the shipment — chosen by you, with the full consequences in view.

Where to find it​

It's built into the everyday adjustment flow — no new screen to learn. Go to Inventory → Adjustments → Add Adjustment, choose a product and a direction, and the impact preview appears as soon as your change would touch allocated stock. The same visibility follows you into receiving against a purchase order, so goods-in and goods-out both tell you what's about to happen before it does.

✨ What this means for you:

• Exchange rates update automatically every day — no more manual entry.
• Every currency converts to your base currency (not just US Dollars), using live cross-rates.
• Pin a custom rate on any currency when you need to — automation leaves it alone.
• Always know how fresh your rates are, and refresh on demand.
• A complete day-by-day history of every rate, so you can see how a currency moved over time.

Set it and forget it​

The Currencies screen now shows a live conversion for every foreign currency, refreshed daily and converted to your base currency. A green Auto chip means that currency's rate is managed for you, and the header tells you exactly when rates were last updated and where they came from.

Keep a custom rate when you need one​

Automation is the default, but you stay in control. Turn a currency's Auto-update toggle off to pin your own rate — the daily refresh will never overwrite it (the Yen above is set manually). Flip it back on and it picks up the live rate again on the next update.

Refresh on demand, with honest status​

Need the latest numbers right now? Click Refresh Rates. And if the rate source is ever unreachable, SKU.io tells you plainly and keeps using your last known rates — it never quietly passes off stale numbers as current.

A history you can look back on​

The new History tab is a searchable, sortable table of every currency's rate to your base currency, day by day. Filter by currency or by date range to see exactly how a rate moved over time — handy for reconciling foreign‑currency orders, bills, and payouts.

Where to find it​

Head to Settings → General → Currencies. The live rates, Auto-update controls, and freshness status are on the Rates tab; the day‑by‑day rate history is on the History tab — which you can bookmark or open in its own tab.

eBay Payout Accounting fixes that. SKU now pulls your eBay Managed Payments payouts, breaks each one into its real components, and posts a single deposit-matched summary to your accounting — one entry that reconciles to your bank deposit to the cent.

✨ What this means for you:

• One summary per payout, not thousands of lines. Each eBay deposit becomes a single clean accounting entry that matches your bank feed exactly — reconcile in one click instead of rebuilding it from hundreds of orders.
• Every component on the right account. Sales, refunds, final value fees, ad fees, shipping labels, and charges are each split onto the account you choose — no more lumping the deposit into one bucket.
• Sync on your terms. Pull just the new payouts, a custom date range, or run a full re-sync — whatever you need.
• Full drill-down. See exactly what makes up any payout, right down to the individual transaction lines, all searchable.

Sync your eBay payouts​

Head to the eBay Finance area and hit Sync Payouts. You choose how much to pull — fetch just what's new since your last sync, re-import from a start date, grab a custom date range, or run a full re-sync. SKU pulls each payout together with its underlying transactions.

See exactly what each payout is made of​

Open any payout to see its full breakdown — gross sales, refunds, fees, and any charges — alongside the line-level transactions behind it. The summary always ties out to the net deposit, so you can trust the number that hit your bank.

Map each component to your accounts​

Decide once where every part of a payout should land in your chart of accounts. Map sales, refunds, and each fee type to the right nominal codes, set fallback accounts, and choose whether to book eBay revenue per order or as a payout-matched summary. From then on, every payout posts itself correctly.

Browse every payout and line​

The Payouts list gives you every eBay deposit at a glance — status, accounting state, net amount, and a quick summary — all filterable and searchable. A dedicated Transactions view lets you drill into the individual lines across payouts whenever you need the detail.

Where to find it​

Open Integrations → eBay → Finance. The Payouts and Payout Mappings tabs are right there — start with Sync Payouts to pull your history, then set your mappings once and let every future payout reconcile itself.

✨ What this means for you:

• Know exactly where a customer stands — outstanding balance, what's overdue, open credits and net receivable, right at the top of the page.
• See how late it really is — a current / 1–30 / 31–60 / 61–90 / 90+ aging bar, plus an overdue worklist ordered oldest-first.
• A real statement of account — open-item or activity, as of any date, ready to view, export to PDF/CSV, or email.
• Chase payment in a click — send the statement or a payment request by email straight from the customer page, with your credit terms and balance filled in.
• No more spreadsheets — the whole accounts-receivable workflow now lives where the customer does.

Money owed, at a glance​

The customer page opens on the numbers that matter for collections: Outstanding, Overdue, Open Credits, Net Receivable and the customer's credit limit with headroom remaining. An aging bar splits the balance into current and past-due buckets, and an overdue worklist lists the late orders oldest-first — each with a Request Payment button right there.

A real statement of account​

Open the Receivables → Statement view to produce a proper statement — as Open items (every unpaid order and its balance due, aged) or as an Activity statement over a date range. Totals foot to net receivable, credits are netted in, and you can export it to PDF or CSV for your records.

Chase payment without leaving SKU​

When it's time to collect, hit Send — email the statement, or a standalone payment request, straight to the customer. The recipient is pre-filled from the customer's billing email, and the subject and message support placeholders like {customer_name}, {total_due} and {payment_instructions} so a polished, personalized note goes out in seconds.

Where to find it​

Open any customer under Contacts → Customers. The Overview tab now leads with accounts receivable, and the Receivables tab holds open orders, credits, the statement and your sent communications.

✨ What this means for you:

• Stop unpaid orders from tying up stock — hold bank-transfer and PO orders as reserved or draft instead of allocating and shipping them like paid orders.
• Reservations that clean themselves up — set an expiry (say, 7 days) and an unpaid reserved order automatically releases its stock if the money never comes, so availability stays honest across every channel.
• Opens itself the moment you're paid — when payment lands, the order flips to open and flows to fulfillment on its own.
• Down to the payment method — cash-on-delivery can ship while a bank transfer waits; set the rule per method, not just per channel.
• Keep your ledger clean — choose whether unpaid orders push to your accounting software as chase-ready invoices, or stay out until they're paid.

Decide what happens to an unpaid order​

Each connected store gets one row. Pick how unpaid orders arrive — Reserve (allocate the stock and hold fulfillment), Draft (don't allocate until you approve), or Open (treat it like a paid order) — and, for reserved orders, how many days to hold before the reservation auto-releases. Turn on Auto-open on payment and the order opens itself as soon as the payment is confirmed.

These rules override your account-wide "Set unpaid orders as Reserved" setting for any channel you configure here — and each row tells you whether it's using its own rule or following the account default, so there's no guessing which setting is in charge.

Down to the payment method​

Not every unpaid order should be treated the same. A cash-on-delivery order ships unpaid by definition, while a bank transfer should be held until it clears. Expand a channel to set an override per payment method — SKU.io discovers the methods automatically from your imported orders — and decide, for each, how the order lands and whether its invoice syncs to accounting.

Keep your accounting clean​

Unpaid orders and your books are two different questions. For each channel you can choose to send unpaid orders as awaiting-payment invoices — so you can chase them from Xero or QuickBooks — or hold them out of accounting until they're paid, or simply follow the channel's usual setting. You get the awaiting-payment invoices you want for collections without cluttering your ledger with money you may never see.

Works across your channels​

The policy is channel-agnostic. It's available today for Magento 1, Magento 2, Shopify, and WooCommerce stores — so the offline-payment orders those storefronts send you all land the way you intend.

Where to find it​

Go to Settings → Unpaid Orders. Edit the row for any connected store, set how its unpaid orders should be handled, and click Save for that channel. Changes apply to newly imported orders.

✨ What this means for you:

• See true profitability, not just gross margin — your allocated marketing, fees and overhead are now subtracted right in the report, so the profit number reflects what you actually keep.
• An industry-standard margin ladder — Gross Profit, Contribution Margin and Operating Profit are named exactly as your accountant expects, with the percentages alongside each.
• Every number explains itself — a click shows the exact cost entries behind any figure, so there are no mystery numbers.
• Overhead broken out by type — see marketing vs advertising vs software as their own columns, per brand, SKU or supplier.
• Compare against last period — each figure carries a change chip versus the previous period or prior year.

A margin ladder, from revenue to operating profit​

The summary now reads as a ladder. Start with Revenue, subtract COGS to get Gross Profit, subtract your direct and indirect costs to get Contribution Margin, then subtract the overhead you haven't tied to a specific product to get Operating Profit — the company-level bottom line. Each tile shows the dollars and the margin percentage, and a small change chip tells you how it moved versus the period before.

Overhead, broken out by cost type​

In the Cost Breakdown view, your allocated overhead appears as an Indirect Costs column that folds into total cost and contribution margin. Expand it and it splits into a column per cost type — Marketing, Amazon Advertising, Software and any type you've created — for every brand, SKU or supplier. Costs that can't be tied to a specific row (a brand-wide fee, or a cost allocated to a product with no sales this period) roll into a clearly labelled Non-Product / Unallocated line, so the totals always add up.

Click any figure to see exactly where it came from​

No figure is a black box. Click the indirect cost on any row and you get the exact cost entries behind it — the campaign or fee, its type, what it was allocated to, the effective period and the amount — and the list totals to the cell you clicked. The Operating Profit tile does the same for the overhead that hasn't been allocated yet, each row linking straight to its cost entry.

Down to the individual order — and your profit alerts​

The same overhead is prorated down onto individual sales orders, so an order's Profit tab now shows its contribution profit — the order's profit after its share of allocated overhead — right beneath the usual profit figure. And if you turn it on in your financial-alert settings, profit alerts can watch contribution margin instead of raw profit, flagging orders that only look profitable before overhead is applied.

Where to find it​

Open Insights → Reports → Profitability Report. Everything is on by default — pick your date range and dimension and click Generate. Use the Include indirect costs toggle to compare margins before and after overhead, and the per-order contribution profit shows on any sales order's Profit tab.

✨ What this means for you:

• Profit and loss by channel — see revenue and margin for Amazon vs Shopify vs wholesale in your own Xero or QuickBooks reports, using the tags SKU.io attaches automatically.
• COGS by channel, not just revenue — the cost-of-goods journals SKU.io generates from your real fulfilment costs carry the channel tag too, so you get true gross margin per channel — not just top-line sales.
• No account proliferation — one tracking category with an option per channel replaces a whole column of duplicate sales and COGS accounts.
• Set it once — map each channel to an option in a single settings screen; from then on every synced document is tagged for you.
• Works with what you already have — pulls your existing Xero tracking categories (or QuickBooks classes) so you map to the ones your accountant already uses.

Map each channel to a tracking category​

Open the new Tracking Categories tab in your accounting settings. Pick the Xero tracking category you want to segment by — most sellers use one named "Sales Channel" — and match each of your connected channels to one of its options. Anything left unmapped is flagged so nothing gets tagged by accident, and you can set a fallback for channels you haven't mapped yet.

Choose exactly which documents get tagged — revenue, cost of goods, and Amazon settlement postings — with a simple set of toggles, so the tagging matches how you want to read your reports.

Create options without leaving SKU.io​

Missing an option for a channel? You don't have to jump over to Xero and back. Create the tracking option — or a whole new tracking category — right from the settings screen, and SKU.io creates it in Xero for you and maps it in one step. (SKU.io respects Xero's limit of two active tracking categories, so it'll tell you when you've reached it.)

QuickBooks Online too​

On a QuickBooks connection the same screen maps your channels to classes instead of tracking categories, so QuickBooks sellers get the same profit-and-loss-by-channel view using class tracking.

Where to find it​

Go to Accounting → Settings → Tracking Categories (it appears once you've connected Xero or QuickBooks Online). Map your channels, save, and your next synced invoices and cost-of-goods journals will be tagged.

✨ What this means for you:

• Every payout, synced — each Shopify Payments payout appears in SKU.io with its status, net amount, and the full breakdown of what made up the deposit.
• Matches the bank to the cent — the summarized entry always equals the deposited amount, so bank reconciliation is a match, not a reconstruction.
• Split, never lumped — sales, refunds, processing fees, and adjustments each post to the account you choose, keeping revenue, tax, and expenses accurate.
• A clean ledger — one summary per payout instead of thousands of per-order lines a month, with per-order posting still available if that's how you work.
• No double counting — switching between per-order and payout-matched accounting is guarded, so revenue is only ever recognized one way.

See every payout at a glance​

The new Finance area in your Shopify integration lists every payout with its payout ID, date, status, net amount, and the charges, refunds, and fees behind it. Filter by payout or accounting status, search by payout ID, and sort any column — held payouts (still in transit at Shopify) are clearly marked and never post until they're paid.

Drill into any deposit​

Click a payout to open its detail page: the summary split shows exactly how charges, fees, refunds, and adjustments add up to the deposit, with a clear confirmation when the numbers balance. Below it, every balance transaction in the payout is listed line by line, linked back to the order it came from.

Route every line to the right account​

Payout Mappings is where you decide where the money goes. Group payout line types into invoice and bill documents, map each financial code to a ledger account, and set fallback accounts so nothing is ever dropped — unmapped lines are flagged and routed to your fallback revenue or expense account until you map them.

Choose how revenue posts — safely​

Prefer payout-matched summaries? Flip the accounting sync mode from Per Order to Per Payout in the finance settings. Because that changes how revenue is recognized, SKU.io asks for confirmation first and explains exactly what will happen — per-order invoices are suppressed while payout summaries carry your revenue, so nothing is ever counted twice. A payout accounting start date lets you choose the exact point the new mode takes effect.

Where to find it​

Open Apps & Integrations → Shopify → Finance. The Payouts tab lists every synced payout (use Sync Payouts to pull the latest from Shopify), and the Payout Mappings tab holds your account mappings and accounting sync mode. Reconnect your Shopify store once to grant the new payouts permission, and SKU.io takes it from there.

✨ What this means for you:

• See the colour, not the word — every option can carry a hex colour or an image, rendered as a real swatch chip.
• Images for patterns and textures — a plain colour can't show a floral print or a wood grain; point an option at an image URL and the swatch shows the real thing.
• Set it once, use it everywhere — a swatch lives on the option itself, so every product that uses that option inherits it automatically.
• Flows to your channels — variant listings carry their per-variant swatch images to marketplaces that support them, starting with Walmart and Shopify.
• One place to manage variants — declare which attributes vary across a product's variations and edit their swatches together, in a single dialog.

Turn any attribute into a swatch​

Every product attribute now has a Display as setting. Leave it as a plain dropdown for descriptive attributes like Size, or switch it to Swatch for anything visual like Colour or Material. Once it's a swatch, each option gets two optional fields: a hex colour and an image URL. Enter #E53935 for a red chip, or paste an image URL to show a pattern or texture — the preview updates as you type.

You'll find this under Settings → Products → Attributes — open an attribute, tick Has Options, and choose Swatch under Display as.

Declare your variants and their swatches in one place​

On a product with variations, the Variant Axes & Swatches dialog does two jobs at once: it declares which attributes actually vary across the variants (Colour, Size, or both), and it lets you edit that attribute's swatches right there — no jumping back to Settings.

Open it from a variant product's Overview tab — in the Variations panel, click Attributes to Compare. Tick the attributes that vary, adjust their swatches, and hit Apply.

Real swatches on your variant products​

Because the swatch lives on the option, every variant that selects that option shows the same chip automatically — nothing to re-enter per child. When you publish a variant product to a channel that supports variant swatches, SKU.io sends each variant's swatch image along with it, so your listing shows shoppers the actual colours and patterns.

Where to find it​

• Set up swatches: Settings → Products → Attributes → open an attribute → Display as: Swatch, then set a colour or image per option.
• Manage a product's variants: open a variant product → Overview → Variations panel → Attributes to Compare.