Every warehouse event, posted in Business Central.
Weave BC sends your released orders to Ongoing within minutes. Every receipt, shipment and return comes back as its own posting, invoiced and credited for exactly what moved. Every night it checks that both systems hold the same stock.
Sign up with your Microsoft work account. One price per warehouse connection.
The Weave console, with sample data.
Everything the warehouse needs, and everything it did.
One Business Central company, one Ongoing goods owner. Documents go out when you release them and come back as postings, each one traceable to the warehouse event behind it.
To the warehouse
Business Central → Ongoing- ItemsNew items and item card changes, every hour. An order's missing items are created before the order.
- Purchase ordersWith supplier, order date, line texts, prices and the supplier's order number.
- Sales ordersOn release, including orders paid at checkout and held at Pending Prepayment, with carrier and customs values.
- Transfers and purchase returnsTransfers in and out, and returns to your suppliers.
Back to Business Central
Ongoing → Business Central- Purchase receiptsOne receipt per delivery, received for your buyers to match the supplier invoice against.
- Sales shipmentsShipped and invoiced for exactly what left, with tracking number and carrier on the documents.
- Customer returnsReceived and credited, sorted to sellable stock or claims by return reason, with your return fee.
- Transfers, adjustments and claimsTransfer receipts and shipments, stock corrections, and a weekly transfer out of the claims location.
The invoice bills what left the warehouse in that shipment.
Weave posts each shipment as its own shipment and invoice. Before it posts, it sets Qty. to Invoice on every line to what this shipment moves, so a part-shipped order bills each parcel once.
- Per event. Every quantity sent to Business Central is what happened in one warehouse event.
- Combine Shipments respected. Those orders ship without an invoice and Business Central's batch job invoices them as before.
- Receipts for matching. Purchase receipts are received only, ready for the supplier's invoice.
- Credit memos that reconcile. Each carries the sale's payment method, payment reference and customer.
Sample data.
Returns land where the reason says.
The return reason the warehouse records decides the destination. A wrong size goes back on the shelf, a defect goes to your claims location, and the credit memo posts in the same step.
- Both kinds of return. Returns on a return order, and returns booked back onto the original sales order.
- Return orders created for you. When none exists, Weave creates it from the sale, with the sale's VAT treatment.
- Your return fees. A table by reason and currency, charged once per return.
- A weekly claims transfer. What sits on the claims bin moves out of the claims location on one transfer order.
Sample data.
Both systems, the same stock.
Every night Weave compares Business Central's stock with Ongoing's, SKU by SKU, sellable and claims apart. Each difference comes with the documents behind it, so you fix the cause.
- Picked counts as in the warehouse until it ships, so a busy afternoon does not look like a gap.
- Oversold lines every 15 minutes: released order lines the warehouse says it cannot pick.
- Backlog by age: late sales orders, purchase orders gone quiet, transfers stuck in transit.
| SKU | Ongoing | Business Central | Status |
|---|---|---|---|
| 178233-3333-38 | 14 | 14 | Same |
| 179354-1001-40 | 6 | 6 | Same |
| 181020-2210-38 | 21 | 21 | Same |
Sample rows. The 0 of 4,632 is Wakakuu's result on 23 September 2026.
One console for both systems.
See what went to the warehouse today, what came back, and the few things that need a person. Every exception says what happened, why, and what to check.
- Exceptions raised once, closed by themselves when a later run fixes them.
- Alerts in Slack and email, chosen per person.
- Orders, shipments, items and stock, with search across all of them and CSV export.
- Microsoft sign-in with admin, operator and viewer roles, and an audit log of every change.
Overview
Synced 2 min agoBusiness Central asks the warehouse before an order is pulled back.
When someone reopens or deletes a sales order or a transfer out, Business Central checks Ongoing first, live. If picking has started, a reopen asks for confirmation and a delete stops with the reason.
If you switch it on, a sales order a person deletes before picking starts is also cancelled in the warehouse, after one more live check.
The message Weave's extension shows in Business Central.
The details a Business Central consultant checks first.
Stored first, then moved
Each Ongoing feed has its own cursor on Weave's side. Events are stored before it moves, so an interruption costs one re-read.
One posting per event
The Ongoing event id is stamped on the posted receipt line, so every posting traces back to what the warehouse did.
Posting twice returns the first
Repeating a posting returns the original document. A lost answer is settled by asking Business Central what it holds.
Item and variant, joined right
Ongoing holds one article per size and colour. Weave splits it into item and variant for posting and joins them for comparison.
A short list of named writes
Every write to Ongoing goes through one list of named operations with its own credential. The readers can only read.
Postings name Weave
Weave signs in to Business Central as its own Entra application and posts through its own extension's routines.
Live one flow at a time.
Create an account
Sign in with your Microsoft work account and name your Business Central company and Ongoing goods owner.
Install the extension
Weave's extension in Business Central, with its permission set and an Entra app registration for Weave.
Run in shadow
Weave records what it would post. A nightly comparison shows it against what Business Central holds.
Switch on per flow
Receipts, shipments, returns and transfers each get their own start time, and alerts go to the people who own them.
One price per warehouse connection.
A connection is one Business Central company and one Ongoing goods owner. Every flow, the console and the alerts are included.
- Every flow in both directions
- Nightly stock comparison, oversold and backlog
- Operations console with Slack and email alerts
- Microsoft sign-in, roles and audit log
- Hosted in the EU
Questions buyers ask.
What is Weave BC?
Weave BC is the integration between Ongoing WMS and Microsoft Dynamics 365 Business Central. It sends items and released orders to the warehouse, and posts what the warehouse did back to Business Central: purchase receipts, sales shipments with their invoices, customer returns with their credit memos, transfers and stock adjustments. It runs as a Business Central extension plus a hosted service with its own operations console.
How quickly do documents move?
Released documents are sent to Ongoing on a five-minute schedule, and warehouse events are read and posted to Business Central on five-minute schedules too. Item card changes go hourly. A purchase receipt waits for a short quiet period so a delivery booked in several rounds becomes one receipt.
Does Weave invoice sales shipments?
Yes. A sales shipment is shipped and invoiced in the same posting, for exactly the quantities that left the warehouse in that shipment. Weave sets Qty. to Invoice on every line before it posts. Orders that use Combine Shipments are shipped without an invoice, so Business Central's own batch job invoices them as before.
How are customer returns handled?
Weave receives each return on a return order and posts the credit memo in the same step, at the return order's own price. The return reason recorded by the warehouse decides whether the goods go back to sellable stock or to your claims location. Return fees come from a table by reason and currency. If no return order exists yet, Weave creates one from the original sale.
What do I need in Business Central?
Business Central online and Weave's extension, which ships its own API pages, posting routines and the WEAVE permission set. Weave signs in as its own Microsoft Entra application, so every posting names Weave's application user.
Can we start with one flow?
Yes. Each flow has its own switch and start time. You can switch on purchase receipts first, then shipments and returns, and Weave can run a flow in shadow first, recording what it would post so you can compare before it posts for real.
Where is our data stored?
In the EU. The service runs on Vercel in Frankfurt and the database is PostgreSQL on Neon in Frankfurt. Credentials for your systems are encrypted at rest with AES-256-GCM.
How is Weave priced?
One price per warehouse connection, meaning one Business Central company and one Ongoing goods owner. We give the price when you create an account or contact us.