11 posts tagged with "Shipping"

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.

When a wholesale order comes in, someone usually has to leave SKU.io, look up a carrier rate, work out a markup and type a shipping line onto the order by hand. Wholesale buyers checking out on your portal often can't see what shipping will cost at all. Shipping cost estimates fix both. Connect your own EasyPost account and SKU.io prices shipping from your warehouse to the customer's address with your carrier rates, contract rates included. You can quote it on sales orders and quotes, show it to buyers at portal checkout, and estimate transport costs for FBA inbound plans.

If you ship orders from your own warehouse, buying the label has always meant leaving SKU.io: copy the address into another shipping tool, guess at the weight, pick a carrier, then paste the tracking number back. It's slow, it invites typos, and the shipping cost never makes it onto the order. Shippo fixes that. Connect your Shippo account and you compare live rates from every carrier on it, buy the label and print it, all from the fulfillment order. SKU.io records the shipment with its tracking and cost, and sends the tracking to your sales channel.

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.

When a vendor ships a dropship order straight to your customer, they usually ship on their own carrier account. You pay their markup, you don't control the carrier, and then you chase them for a tracking number and type it in by hand. Dropship vendor shipping labels fixes that. Switch it on for a supplier, and SKU.io buys a prepaid label on your own Shippo, ShipStation, Starshipit or EasyPost account and gets it to the vendor. The label's tracking flows back into the order by itself, so your customer and sales channel hear "shipped" at the right moment.

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.

If you buy or sell across a border, the Incoterm is one of the most consequential fields on the order — it decides who pays the freight, who insures the goods, who clears customs, and the exact moment risk stops being yours. Until now, SKU.io treated it as little more than a note: a free-text code on purchase orders, nothing at all on sales orders, and no explanation of what any of it meant. Incoterms changes that. The 11 official ICC Incoterms® 2020 rules now ship built into every account with plain-English education, a term on an order is a complete value — code, named place, and edition — that's locked into history, and every screen that touches a term can explain exactly who is responsible for what.

A tracking number on its own doesn't tell you anything. To find out whether an order actually reached the customer — or whether a supplier shipment is anywhere near your dock — you had to copy the number, open the carrier's website, and check shipments one at a time. Failed deliveries and stalled packages stayed invisible until a customer complained or a receipt came up overdue. 17TRACK Delivery Tracking changes that: connect your own 17TRACK account and SKU.io registers every new tracking number automatically, pulls live carrier status for it, and shows a delivery-status chip beside the tracking number everywhere it appears — across outbound fulfillments, purchase order inbound shipments, warehouse transfers, customer returns, and shipments back to vendors.