75 posts tagged with "Integrations" — Page 2

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.

A thousand units at a fulfillment center in California do little for a buyer in Ohio. Marketplaces place your stock where it suits them, and until now SKU.io showed it as one number per network, so you couldn't tell that most of a SKU sat on the West Coast while a third of its buyers live in the East. Regional coverage adds that missing view to the Send Planner. For every SKU and network, it estimates the share of buyers within two days of your stock, shows which regions are thin, and shows what this plan's send does about it. You can also play back how your stock spread over the last months.

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.

SKU.io already tells you where you owe sales tax. Acting on it has meant exporting a report and re-keying it into a filing service, which only ever sees the one channel it's connected to. Wholesale and B2B orders you create in SKU.io aren't on any channel, so a filing service connected to Shopify or Amazon never sees them at all. Numeral is now a SKU.io integration. Connect your own Numeral account, and SKU.io sends it every sale and credit from every channel, including the orders you create in SKU.io. Numeral then handles your registrations, filings and payments.

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.

Every online store we have run sat on a CMS: an admin login, a stack of plugins and a theme, each one something to patch, defend and pay for. Stores are built differently now. A coding agent can write any design you can describe, so the store doesn't need a screen for a person to click through. It needs a standard, an API, and the freedom to look like anything. So we built one. Storefront is our open-source store kit, with no CMS in the middle, and starting today SKU.io connects to a Storefront store as a sales channel. Orders flow in, and stock, tracking and products flow back out, with no plugins and no keys to copy.

You already ask an AI assistant to draft emails and summarise documents. But when the question is "how much of this do we have, and is more on the way?", it has nothing to go on, so you end up copying numbers out of SKU.io by hand. The new MCP Server connects SKU.io to the assistant you already use: Claude, ChatGPT, Cursor or any other assistant that supports MCP connectors. Add one link, sign in to SKU.io, and the assistant answers from your live products, stock, orders and purchase orders. If you allow it, it can also do the routine work, such as drafting a purchase order or recording a supplier invoice.

Some jobs happen one record at a time: add the standard note to an order, flag it for the warehouse, update a supplier in your accounting system. Until now, a workflow could only start on its own, from a schedule or an event, so these jobs stayed manual. Record automations let you run a workflow by hand on the record you're looking at. Open a supplier, product, sales order, purchase order or customer, click the lightning bolt at the top of the page, and pick what to run. A workflow can even hand the job to a script or an AI agent on your own computer, and report the result back on the record.

Your 3PL counts the stock on its shelves, and SKU.io keeps its own count of the same stock. When the two drift apart, you either sell stock that isn't there or hide stock you could be selling — and comparing them by hand is unreliable, because orders keep shipping while you look. 3PL inventory comparison checks the two against each other automatically, every day, warehouse by warehouse. It rewinds SKU.io to the exact moment the 3PL counted, so a shipment in flight never shows up as a false difference. Where the 3PL is right, you accept its count and SKU.io creates the stock takes for you.

If your team automates with n8n, connecting it to SKU.io used to mean building every step by hand: an HTTP request for each call, a token pasted into headers, and a webhook wired up separately for each event. SKU.io now has its own node in n8n. Search for SKU in the nodes panel, install it, connect your account once, and your workflows can start the moment something happens in SKU.io and create or find SKU.io records from any other step. The node carries n8n's verified badge, so it installs on n8n Cloud as well as on your own n8n server.