Shipping Station Workflow

Connect your selling channels with your assistant.

Batches of marketplace orders become reviewed stock movements in your own TeamDesk database. Your assistant does the connection work with you - you step in where your own login or approval is needed.

See the working demo

Worth saying plainly: the demo runs on its own sample data. No platform below is connected in the demo. Each route is connected, mapped and tested when the workflow is set up for a real business.

A seller's day

Who this is for, and what their day actually looks like.

Sells on	eBay, Amazon and often their own WooCommerce store
Ships with	ShipStation, on their own account
Size	One person to a small team
Stock	One physical pool, listed in several places at once

Overnight, orders arrive from every channel and collect in ShipStation.
Morning is batch, pick, pack and print labels. ShipStation is genuinely good at this part.
All day, the same physical stock sits listed in three or four places, each keeping its own count.
A kit sold on one channel should reduce its components everywhere. Without kit mapping in place, it does not - someone fixes it by hand, or it stays wrong.
Evening is exports, a spreadsheet or an ageing ERP - and hoping nothing oversold.

Where it hurts

Five places the routine breaks down.

1. Every channel keeps its own countSell on eBay and the Amazon listing keeps the old number until something updates it. Sync tools can keep channels aligned when they are set up and maintained well; the sellers who come to us are the ones still stitching it together by hand - and that is when the same unit sells twice. Amazon punishes overselling hard.

2. One product, many namesA listing title on eBay, an ASIN on Amazon, a SKU on the shelf. When the mapping breaks, counts drift silently and the error surfaces only when a buyer is let down.

3. Unmapped kits never break into partsA bundle only reduces its components when someone has mapped the kit to its parts. Until then, component counts go wrong on every sale. Multi-channel sellers describe building their own workarounds for exactly this.

4. The glue is manualReports downloaded, corrected, pivoted in Excel, imported somewhere else. Every hand-off is a place to be wrong, and it is someone's evening.

5. They have been burned by automationSellers who lost money to a system that guessed want a person checking before stock moves. Full autopilot is a deal-breaker, not a feature.

Sources: multi-channel overselling · multi-channel inventory tracking · Linnworks on overselling · a seller on bundles in ShipStation · Shopify community on overselling

How we help

The daily shipping routine, turned into a conversation and a review.

Takes the order batch your shipping platform already produces and turns it into reviewed stock movements.
Matches marketplace listing names and kits to your real stock-keeping units using saved rules, and breaks kits into their components.
Holds anything it cannot resolve for a person's decision. It never guesses, and nothing posts to your stock without a person's approval.
Every movement traces back to its source order lines, so your stock on hand is always explainable.

The journey

First conversation: two questions - what do you ship, and where do you sell it? We work out what your version looks like before anything is built.
Setup is done with you, not to you. Your ShipStation account stays yours. The assistant connects eBay, Amazon and WooCommerce; you authorise each platform at its own sign-in screen. The whole path is tested end to end with a real order at setup.
Each order batch lands as staged lines in your own TeamDesk database. Waiting, not posted.
Saved rules match listing names to real SKUs. Kits break into their components.
Anything the rules cannot resolve is held for your decision. It is never guessed.
You review and approve. Only then do stock movements post - each one traceable back to the exact order lines behind it, so the stock count is always explainable.
The assistant stays on: it explains the screen, walks you through exceptions, and answers questions in the same popup chat on this page and inside the database.

What changes for you

One stock count you can explain - instead of separate channel numbers that drift apart when nothing reconciles them.
The spreadsheet glue goes - orders flow into reviewed stock movements; the evening export-and-pivot ritual ends.
Control stays with you - nothing posts without a person's approval, and every movement shows its source orders.

The assistant

Not a platform to connect - it's who does the work.

You talk to it in chat, like WhatsApp. It carries the connection work on this page, then the daily batch work afterwards: explaining what came in and why, preparing the next batch, answering questions about your stock. It proposes - you decide. A person approves every posting.

Hear the ShipFlow guide explain the working demo - voice or text, straight from the browser.

eBay

Orders from your eBay store, via ShipStation.

You need: An active eBay seller account, and your eBay login.
The assistant: Opens ShipStation, goes to Account Settings > Selling Channels > Store Setup, chooses Connect a Store or Marketplace, picks eBay and starts the connection.
You step in: At eBay's own sign-in and authorisation screen. Your account, your approval - the connection can't complete without you. eBay asks sellers to re-authorise the connection about once a year.
After that: New eBay orders appear in ShipStation automatically (each order needs a ship-to address and at least one item). When a label is created, ShipStation sends the status and tracking number back to eBay for you. From ShipStation, order batches are handed to your database for review - that leg is configured and tested separately at setup. Selling on more than one eBay account? Each store is connected in its own private browser window so the logins don't get crossed.

Source: ShipStation's eBay connection guide

Amazon

Orders from Amazon Marketplace, via ShipStation.

You need: An Amazon Seller account on the Professional plan, and your Seller Central login.
The assistant: Follows the same Store Setup path in ShipStation, picks Amazon, then chooses your marketplace country and whether your products are identified by SKU or ASIN.
You step in: At the Amazon sign-in, then the authorisation tick box that directs Amazon to give ShipStation access to your Selling Partner account - and Confirm.
After that: Your merchant-fulfilled orders import, and shipment confirmations go back to Amazon automatically. Orders need to be merchant-fulfilled and include a physical product; Amazon-fulfilled (FBA) orders can be imported as shipped orders so you can see them alongside the rest.

Source: ShipStation's Amazon Marketplace guide

WooCommerce

Orders from your own WordPress store, via the ShipStation plugin.

You need: WordPress 6.8 or later running WooCommerce, the free ShipStation plugin (version 4.9.1 or later), and your store URL.
The assistant: Installs and activates the ShipStation plugin in your WordPress admin, opens WooCommerce > Settings > Integrations to collect the three connection codes (Authentication Key, Consumer Key and Consumer Secret), enters them in ShipStation's Store Setup, and runs Test Connection before saving.
You step in: Approving a plugin on your own site. The three codes are your store's credentials - they're handled as secrets and never pass through chat.
After that: WooCommerce orders import into ShipStation (they need a ship-to address and at least one physical product), stay in sync, and your customers get shipping-confirmation emails.

Source: ShipStation's WooCommerce guide

ShipStation

The middle leg - where marketplace orders gather before they reach the database.

You need: A ShipStation account on a plan that suits your order volume. The account is yours and billed to you.
The assistant: Connects your selling channels (the sections above), sets up your carriers, and sets up the order-batch handover into your database - then tests the whole path end to end, from a real order to a reviewed stock movement.
You step in: Creating the account and choosing the plan.
After that: Marketplace orders arrive as batches in the database, ready for review. Nothing posts to your stock without a person's approval.

Other connections

Standard bridges, designed into every database.

Beyond the named platforms, the database itself speaks REST and webhooks - Call URL actions, triggers and email in and out. On top of that: Zapier has a built-in TeamDesk app; Make and IFTTT reach the database through their standard HTTP and Webhooks services. If a platform your business relies on isn't listed here, that's the conversation to have - bridges are scoped case by case.

Sources: TeamDesk REST API · Call URL actions · Webhooks · TeamDesk on Zapier · Make HTTP modules · IFTTT Webhooks