If your team plans in Airtable — merchandising calendars, purchasing boards, ops trackers — keeping it in step with SKU.io has meant CSV round-trips or a paid middleware subscription that breaks the moment either side changes. The new Airtable integration removes the bridge entirely: connect your Airtable account and SKU.io syncs your operational data both ways, on a schedule or in near-real-time. Push products, inventory, orders, purchase orders, and suppliers into your own Airtable base — or let SKU.io build a ready-made base for you in one click — and when someone edits a safe field in Airtable, review the change before it updates your catalog. It's a first-party, two-way connector with nothing in the middle.

If you sell on eBay, you know the pain of month-end reconciliation. An eBay Managed Payments payout is a single net deposit that quietly bundles your gross sales, refunds, final value fees, ad fees, shipping-label costs, and adjustments — so the number that lands in your bank is none of your revenue figures. Matching it back to your books by hand takes hours, and coding the whole deposit to one income account quietly misstates your revenue, fees, and tax.

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.

When a customer checks out with an offline payment method — a bank transfer, a purchase order, a "pay on delivery" — the order lands in SKU.io unpaid, yet until now it behaved exactly like an order you'd already been paid for: it allocated your stock immediately and could sail straight through to fulfillment. So a wire that might never arrive could quietly tie up inventory for weeks, and there was no way to say "hold this until the money's in." The new Unpaid Orders settings let you decide, per sales channel, exactly how an unpaid order is handled — bring it in as a held reserve with an automatic expiry, park it as a draft for review, or treat it as open and let it ship — with per-payment-method overrides and control over when it reaches your accounting software.

The number Shopify deposits into your bank account is never your sales number. Every payout bundles sales, refunds, processing fees, and adjustments into a single net amount — so at month end someone has to reconstruct each deposit from dozens of individual invoices, or worse, book the whole thing to one income account and quietly misstate revenue, tax, and fees. SKU.io now syncs your Shopify Payments payouts and can post one summarized accounting entry per payout — sales, refunds, fees, and adjustments each routed to the right ledger account, with the net matching your bank deposit to the cent. When the deposit appears in your bank feed, it reconciles in one click.

When a product comes in five colours, "Red", "Blue" and "Green" in a dropdown tell you almost nothing — is that red a crimson or a brick? And for anything with a pattern or texture, a word can't describe it at all. Shoppers pick with their eyes, and so do the marketplaces you list on. SKU.io now supports swatches — give each option of a product attribute a colour chip or a small image, and that swatch shows up on your variant products and flows out to the channels that support variant swatches, like Walmart and Shopify. No more guessing which "Red" is which.

Shopify's profit and margin reports are only as good as the Cost per item you enter on each product — and that number goes stale the moment your costs change. Keeping it up to date by hand across a whole catalog is tedious, easy to forget, and the reason so many Shopify profit reports quietly drift out of line with reality. SKU.io now syncs your costs to Shopify for you. Turn on Cost Sync for a Shopify store and SKU.io pushes each mapped product's real average cost into Shopify's "Cost per item" field — so Shopify's own profit reports, and any margin app that reads that field, finally show the truth.

Until now, getting data out of SKU.io meant polling the API, exporting spreadsheets, or asking a developer to build something custom. Want a Slack message when goods are received? A Google Sheets row for every new sales order? A customer added to your email tool the moment they first buy? Each one was a mini engineering project. SKU.io now has a native Zapier integration, powered by a new outbound webhooks platform — when something happens in SKU.io, SKU.io tells the outside world about it, in real time. Connect the official SKU.io app on Zapier — now live in the Zapier App Directory in beta — and build those automations in minutes, or point a webhook at your own endpoint and build anything you like.

When your FBA inventory hits zero, the ASIN goes dark: the Buy Box disappears, rankings decay, and sales stop until your next shipment checks in — often weeks later. The standard workaround is a "backup" merchant-fulfilled offer on the same ASIN, but keeping it live all the time means it can steal the Buy Box while FBA still has stock, and zeroing it in and out by hand doesn't scale past a handful of SKUs. FBM Backup Mode automates the whole dance: SKU.io publishes 0 to your merchant-fulfilled (FBM) listing while a linked FBA offer still has sellable stock, then publishes the real quantity the moment FBA runs out — and re-suppresses it automatically when FBA is replenished. Your offer never flips fulfillment type and never leaves the ASIN; it just waits its turn.

If you sell on Magento 2 (Adobe Commerce), keeping your store and your inventory system in agreement has meant CSV exports, copy-paste order entry, and stock levels that drift out of date the moment they're published. The new Magento 2 integration connects your store to SKU.io as a first-class sales channel: orders, products, customers, and transactions flow into a dedicated workspace, SKU.io sales orders are created from Magento orders in bulk or automatically, and on-hand quantities push back to your store's inventory sources on a schedule.

Until now, listings only ever flowed into SKU.io. To actually put a product up for sale you still had to log into each channel's seller portal — eBay Seller Hub, Shopify admin, Amazon Seller Central, Walmart — and re-key the same title, description, images, price, and attributes, once per channel. And because every marketplace requires different fields per category, you often didn't discover a missing attribute until the channel rejected the listing.

Multichannel Listing & PIM closes that gap. SKU.io now doubles as a Product Information Management hub that can publish new listings to and update existing listings on every connected sales channel — so your catalog is the single source of truth and each channel stays in sync with it.