Release Notes — Page 6

A product can have thousands of units in your own warehouse and none at Amazon, and a stock check that looks at your business-wide total never notices. By the time Amazon stops selling it, you've lost sales and Buy Box ranking that takes weeks to win back. FBA minimum stock levels let you set the least stock you want at each Amazon FBA region, product by product, as a fixed number of units or as days of cover. SKU.io checks every minimum each time Amazon's inventory updates, and when a product drops below it, an FBA Low Stock alert opens a new inbound plan with the product and a suggested quantity ready to add.

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.

The report builder covers most questions in a few clicks. But sometimes you need to rank products against each other, compare one period with another, or combine data in a way the builder can't express. Until now, those reports meant waiting on someone to build them for you. SQL reports let the people on your team who know SQL write the report themselves, as a query, right inside SKU.io. The query runs read-only against your own data, and the result is a normal saved report you can share, schedule and export.

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.

You rolled out SKU.io to your team, but did it stick? Is the purchasing team actually receiving POs in SKU.io, or still working from a spreadsheet? Which features are you paying for and never touching, and which ones could save you hours if someone switched them on? Until now there was no single place to answer that. The new Feature Adoption report maps every SKU.io feature by area, shows which ones your team uses and who uses them, and points out what you haven't tried yet. When a feature will never fit your business, you can hide it so the report stops suggesting it.

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.

Suppliers sell liquids by volume — a gallon of agave syrup, a drum of oil, a pint of extract. Recipes and stock counts use weight. Those are different kinds of measurement, and the number that connects them is different for every ingredient: a gallon of syrup and a gallon of oil do not weigh the same. Until now, the only way through was to invent a unit per ingredient and type the factor in yourself — a step that quietly goes wrong at receiving and turns into an argument with a supplier about what the purchase order should have said. Density conversions replace that with one number per product. Set the density, and every conversion between a volume unit and a weight unit is worked out for you, with its arithmetic shown on the row.

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.