76 posts tagged with "Integrations" — Page 4

Selling to big-box and department-store retailers means trading over EDI. Their purchase orders arrive as electronic documents through a network like SPS Commerce, and they expect electronic replies: an acknowledgment that you accepted the order, and a ship notice when it leaves your dock. Until now that meant re-keying every order by hand and hoping the replies went out on time. The SPS Commerce integration connects your SPS Commerce account to SKU.io, turns each retailer purchase order into a sales order, and sends the acknowledgment and ship notice back for you.

When ShipBob runs your warehouse, the day-to-day work splits across two systems. Orders have to reach ShipBob, tracking has to come back to your sales channels, and ShipBob's stock count drifts from yours. Then the weekly invoice arrives as a list of pick fees, packaging, surcharges, storage and freight that never makes it onto the orders and products that caused it. The ShipBob integration connects the two. Fulfillment orders go to ShipBob automatically, shipments, tracking, stock, returns and receiving come back, and every ShipBob charge is matched to the order, product or purchase order behind it, so your margins show what fulfillment really costs.

Amazon loses and damages FBA inventory, receives shipments short, refunds customers for returns that never come back, and overcharges fulfillment fees when it measures a product wrong. It owes you for all of it, but it rarely pays unless you ask: you have to spot each problem in its reports, prove it, and file a case before a short claim window closes. Most sellers either let that money go or hand a recovery agency a cut of everything recovered. Amazon Recovery does the finding, the evidence and the writing for you. It shows what Amazon owes you, writes every claim, walks you through filing it in Seller Central one case at a time, and tracks Amazon's answer until the money arrives.

Amazon now lets business buyers require that bulky items, such as racking, decking and workbenches, arrive on a pallet. If one of those ships as an ordinary parcel, it can be refused at the dock, and that hurts your seller metrics. Until now nothing in SKU.io told you which orders needed a pallet. Amazon pallet delivery fixes that. When an Amazon order requires a pallet, SKU.io flags it on the order and on each affected line. It warns you again in the fulfill dialog, and lets you filter your whole order list down to pallet orders.

Your checkout says "Free Shipping" to everyone. But free shipping to Ohio and free shipping to Berlin are not the same job — one goes USPS, the other goes DHL Express. Until now SKU.io could only map that label to a single shipping method, so sellers had two bad options: rename the rates in Shopify so every market got its own label, or fix the carrier by hand after the order landed. Shipping method conditions remove the choice. A channel shipping method can now carry ordered conditions that override its default mapping for specific destinations, so one label routes correctly everywhere.

Publishing a product to a marketplace means telling that marketplace which of its categories the product belongs in — and every channel has its own category tree, with its own names, at its own depth. Done product by product, that is one decision per product per channel, repeated forever, and repeated again for every product you add next month. From today you can answer it once instead. Product types are a small tree you build yourself — "Baby clothing › Accessories › Hats & beanies" — and each type maps to one category per channel. Fifteen beanies become one decision. The sixteenth beanie, added next month, inherits the answer.

If you sell on Amazon both ways — Fulfilled by Amazon and merchant-fulfilled, where you ship the order yourself — you already know the two rarely want the same price. You carry the shipping on an MFN order, the Buy Box behaves differently, and until now the only way to price those listings apart was to pin them one at a time. The Amazon MFN pricing lane fixes that at the channel level: your merchant-fulfilled listings follow their own sequence of price levels, checked before the channel's FBA levels and falling through to them whenever a product has no MFN price. The channel's Pricing page now says which lane priced every listing, and a new Set Pricing action on the listings table lets you pin — or reset — a whole selection of listings in one go, with a preview of every price that would change.

If you sell wholesale through Shopify, you have probably been maintaining two sets of prices. The real ones live in SKU.io — the tier a customer sits on, the contract you agreed with them, the break they hit at 25 units — and then someone re-enters an approximation of all that into Shopify by hand, and it drifts from the day it's typed.

B2B pricing for Shopify removes the second set. SKU.io works out what each wholesale buyer should pay, using the same pricing rules that already produce your quotes and invoices, and publishes those prices to that buyer's company location in Shopify. Your buyers log into your storefront exactly as they do now, and see their own negotiated pricing.

Nothing reaches your storefront until you have looked at a preview and approved it.

There has been a Master of Price setting on your sales channels for a long time, and on all but one of them it did less than it looked like it did. Setting it to SKU.io stopped the channel's price from overwriting yours on the way in — but it never sent anything out. You'd change a price in SKU.io, watch the channel keep charging the old one, and have no way to tell the difference between "it hasn't run yet" and "it was never going to run".

Price sync closes that loop. On Amazon, BigCommerce, eBay, Faire, Magento 1, Magento 2, Shopify, Square, Temu, TikTok Shop, Walmart and WooCommerce, SKU.io now publishes your price to the channel on a schedule you choose — behind guardrails that stop a bad number reaching a marketplace, and with a run history that tells you what happened to every listing.

Every channel has a standard set of product fields, and then it has yours. The care instructions you added as a Shopify metafield. The country_of_manufacture and warranty_months attributes your Magento store has carried for years. That data is real, it's maintained, and until now SKU.io imported none of it — it read the fields every channel has and dropped everything else on the floor, leaving you to re-enter it by hand or accept a catalog that knows less than your storefront does. Channel attributes closes that gap. SKU.io now discovers the attributes your channel actually sends, shows you how many products carry each one and what the values look like, and lets you point them at any SKU product field — either once, when a product is first created, or on every sync, with drift detection watching for changes.