Plays well with what you already run.
Orders arrive from your sales channels, invoices land in your accounting, your 3PL picks and ships, your forwarder reports in, your mailbox is read — no re-keying, no exports, no extra licence for any of it.
- Shopifyproducts & inventory out · orders in
- Your mailboxthreads read in · replies sent out
- MYOB and Xeroinvoices & bills out · payments in
- Your 3PLorders out · despatches & counts in
- API and webhooksread & write · events pushed out
- Forwarders and carriersETAs, milestones & documents in
Weavwork holds the record. Everything around it reads from it or writes to it — in the directions shown, at the moments that matter, without anyone exporting a file.
What flows in, what flows out, and when.
Each connection is part of the one plan. This is exactly what moves across it.
Products and inventory flow to the store; orders flow back as sales orders and fulfil like any other. The SKU tree maps to Shopify products and variants, so the store and the system never disagree about what a thing is. Retail stores run Shopify POS the same way.
- Flows in
- Orders, customers, payment status
- Flows out
- Products, variants, prices, stock levels
- Runs
- Continuous — webhooks both ways
Confirmed orders push to the warehouse to pick and pack; despatches, tracking numbers and stock counts flow straight back onto the order. Wholesale and e-commerce alike. A live connector today; more warehouses added on request.
- Flows in
- Despatches, tracking, receipts, stock counts
- Flows out
- Orders to pick, inbound shipments (ASNs)
- Runs
- On confirmation, on despatch, nightly counts
Invoices and bills flow to your accounting, matched to their orders and shipments, so nothing is keyed twice and month-end reconciles itself. Weavwork is not a ledger and does not try to be one — your accountant keeps the tool they know.
- Flows in
- Payments received, bills paid, contact changes
- Flows out
- Sales invoices, supplier bills, credit notes
- Runs
- On invoice, on bill, on payment
ETAs, milestones and documents arrive on the shipment from your forwarder or carrier, and stock in transit stays bookable until it lands. Landed cost is built from the freight, duty and clearance charges as they come in.
- Flows in
- ETD, ETA, milestones, documents, charges
- Flows out
- Bookings and packing lists, where the forwarder takes them
- Runs
- As the forwarder or carrier posts
Connect Microsoft 365 or Google Workspace and the inbox agent reads each thread against the right production order, sample request or shipment. Summaries on the record, replies sent from your own address, the answers filed where the work is.
- Flows in
- Supplier and customer threads, attachments
- Flows out
- Replies you choose, from your address
- Runs
- As mail arrives; replies when you send
For your IT person, your consultant, or the marketplace we have not named: read and write every record through the REST API, and let webhooks tell your other systems the moment something changes — an order confirmed, a run progressed, a container landed.
- Flows in
- Anything your system writes: orders, stock, customers
- Flows out
- Signed event webhooks and every record on request
- Runs
- Real time; events retried with backoff for 24 h
For the system we haven’t named.
Every record is readable and writable through the REST API, and every change can fire a signed webhook to whatever you point it at — a marketplace, a BI tool, the warehouse we have not connected yet. The payload carries the record, not an ID you have to go and fetch.
- Scoped per-customer keys, signed events, TLS everywhere
- Retried with backoff for 24 hours if your endpoint is down
- Every write on the audit log, with the key that made it
Three things we don’t try to be.
A manufacturer already runs good tools for some jobs. Weavwork connects to them instead of replacing them badly.
Tell us what you run and we will tell you how it connects.
Most requests are a warehouse, a marketplace or a courier we have not named here. Bring the list to the demo — the answer is usually the API, and sometimes a connector we already have.
Book a demoThe ones we get asked.
Which system is the source of truth for products?
Weavwork. The SKU tree defines the product; Shopify receives its products and variants from it. Stock levels are pushed from Weavwork so the store never oversells against a carton that is already allocated.
Does an integration cost extra?
No. Every connection on this page is in the one plan. There is no per-integration licence and no marketplace app to buy.
What if our 3PL is not the one you connect to today?
Tell us who you use. Most warehouses expose an API or an EDI feed we can connect through; the demo is the place to bring the name.
Can we run two Shopify stores?
Yes — a wholesale store and a retail store, or two brands, each mapped to its own price list and fulfilled through the same warehouse.
How is the API secured?
Per-customer API keys with scoped permissions, signed webhooks, TLS everywhere, and every write recorded in the audit log with the key that made it.
Why is the Xero chip text only?
The integration is live; the logo waits on Xero’s partner program. We show a logo only when the platform’s brand guidelines let us.
See your stack connected.
A 30-minute demo, run on your products, your store and your warehouse. No slides.
Or write to hello@weavwork.com