26 posts tagged with "Fulfillment"

If your warehouse prints its labels in ShipRush, every order used to mean typing it into ShipRush by hand, then copying the tracking number back so your sales channel could tell the customer it shipped. Label costs stayed in ShipRush, and nothing stopped the warehouse from shipping an order you'd already cancelled. The ShipRush integration connects the two. SKU.io keeps an order feed that ShipRush picks up on its own schedule, your team rate-shops and prints in ShipRush as usual, and each label comes straight back to SKU.io as a shipment.

Ship with Walmart gives you Walmart's negotiated carrier rates, and Walmart regularly adds shipping credits on top. But if a 3PL packs your Walmart orders, a label you buy yourself never reaches them, and they buy their own postage anyway. So you either skip Walmart's rates or pay for shipping twice. Walmart labels for 3PL orders closes that gap: SKU.io buys the Walmart label for each order going to your 3PL, sends it to them with the order, and tells them plainly to ship on it.

Most merchants arrive at SKU.io with their 3PL or shipping app already plugged straight into their store. Moving that channel over to SKU.io used to be a careful, manual hand-off: switch off the provider's store connection, work out which was the last order it imported, wait for that order to ship, and only then let SKU.io start sending. Get the timing wrong and an order goes to the warehouse twice — and the customer gets two parcels. Provider cutover turns that hand-off into a guided step on every shipping provider, and SKU.io now refuses to send an order your provider already has, so you never ship an order twice when you switch to SKU.io.

Many of the retailers you wholesale to don't want to hold your stock at all. They sell it on their own store and want you to ship each order straight to their customer, without a price or your name on the box. Until now that meant re-keying orders from emails and spreadsheets, hand-swapping packing slips, and chasing tracking numbers to send back. Dropship for retailers turns this into a proper program. You switch it on per retailer and choose how they send you orders. SKU.io ships each one blind, under the retailer's branding, and every shipment's tracking goes back to them automatically.

When you're stuck on a screen, the answer usually lives in a guide on another tab. You search for it, read it, then switch back and try to remember which button it said to click. In-app guides bring that help to you. Open the guide on any SKU.io screen and it slides in beside the page, with the summary, the video walkthrough and the numbered steps for exactly what you're looking at. You can follow along without leaving your work.

Walmart promises every buyer a ship date, worked out from each listing's lag time. If you sell the same product from a fast warehouse and a slower one — your own 3PL and Amazon FBA through Multi-Channel Fulfillment, say — one fixed lag time is always wrong for one of them: too slow while the fast warehouse has stock, too optimistic once only the slow stock is left. Automatic Walmart lag time fixes that. SKU.io gives each listing the lag time of the fastest warehouse that actually holds its stock, tells Walmart the slower lag time before more orders are promised the fast date, and never sends more than the lag time Walmart has approved for your store.

When one 3PL runs both your parcel shipping and your large-item home deliveries, a warehouse never has just one way out. Metro deliveries go to the delivery team, while FedEx parcels ship from the 3PL's own warehouse system. Until now a warehouse in SKU.io had a single shipping provider, so the other half of the orders had to be split off by hand. Two things change that. The new Pinnacle integration sends your home deliveries to Metropolitan Warehouse & Delivery (MWD) and tracks them back. Shipping-method routing lets one warehouse send each shipping method to the provider that should handle it.

Amazon and Walmart grade every seller on how they ship: valid tracking, late shipments, cancellations, order defects. Miss a target and the marketplace can restrict a category or your whole account — and the first you usually hear of it is an email after the damage is done. When an account ships a handful of orders a month, a single bad shipment is enough to tip a score below the line. Channel Health brings those scores into SKU.io every day, warns you before a target breaches, and flags the individual shipments that are about to count against you while there's still time to fix them.

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 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.