Ongoing WMS and Business Central. It just flows.
Orders reach the warehouse when you release them. Receipts, shipments and returns come back as postings, one per event.
Overview
Live, updated 12s agoSent to WMS today174orders and transfers
Posted to ERP today219one per event
Open exceptions2each raised once
Stock in sync0SKUs differing
Flows today↗ sent to WMS, ↙ back to ERP
Sales
↗158sales orders
↙146shipments invoiced
Returns
nothing to send
↙31credited
Purchase
↗13purchase orders
↙36receipts
Transfer
↗3transfers
↙2received
Stock
nothing to send
↙4adjustments
Needs attention2 open
Over-delivery: received 7, ordered 5, above the tolerancePO-104233
Item blocked in Business Central, so its receipt waits10442-BLK-M
The Weave Overview, with sample data.
Both directions, every few minutes.
To the warehouse ERP → WMS
- Items new items and changes, every hour
- Purchase orders and purchase returns
- Transfers in and out
- Sales orders including orders paid at the checkout
Back to Business Central WMS → ERP
- Purchase receipts received, never invoiced
- Sales shipments shipped and invoiced for exactly what left
- Customer returns received and credited, return fee by reason
- Transfers and stock adjustments
Built to be correct.
The things a Business Central consultant checks first, and how Weave answers them.
Cursors that advance lastEach Ongoing feed has its own cursor, stored on Weave's side. It moves only after the events are stored, so a crash costs one re-read, never a lost event.
Nothing read twiceOngoing's lot ids repeat and its fromId is inclusive. Rows are matched by content within their lot, so a re-read inserts nothing.
One posting per eventNever a running total. The Ongoing event id is stamped on the posted receipt line, so every posting traces back to what the warehouse did.
Retries that cannot doublePosting the same event again returns the original document. A lost answer is settled by asking Business Central, never by sending again blind.
Invoiced for what moved
Qty. to Invoice is set on every line, on every posting, to what that posting ships or receives. Never the whole order.Read-only by constructionThe clients that read Ongoing cannot write. Every write goes through one short list of named operations.
!
The warehouse has started on order SO-10231 (Picking), so it can no longer be cancelled there. Call the warehouse before deleting it here.
OK
It asks the warehouse before anyone pulls an order back.
Reopening or deleting a sales order in Business Central checks Ongoing first, live. Once picking has started, a reopen asks for confirmation and a delete is refused, with the reason.
Running at Wakakuu since September 2026.
1,198shipment lines in one week, every one found in Business Central
0 of 4,632SKUs differing between Ongoing and Business Central on 23 September
52 returnsposted as 28 credit memos on the first day returns went live
A fair price, and a simple one.
One price per warehouse connection, on request. Weave is in early access, so we give the price when we reply.