One Business Central company, one Ongoing goods owner, both directions.
What moves, how often, and how every posting stays correct.
To the warehouse, when you release.
Released, then sent
Weave's extension queues every released document that touches the warehouse. Weave sends the queue every five minutes and marks each row in Business Central with the result, so the person who released it sees it where they work.
Items
New items are created in the warehouse and item card changes reach it every hour. A new order's items are created in Ongoing before the order that needs them. Items missing a barcode or net weight are held and listed with the reason.
Purchase orders
With the supplier, order date, line texts, prices and the supplier's own order number. Released again after a change, the order is restated in the warehouse.
When the warehouse closes a purchase order that is still partly outstanding, Weave can send the remainder as a follow-on order, PO-104233-R2 after PO-104233, so a second delivery has an order to arrive on.
Sales orders
Sent on release, including orders paid at checkout that Business Central holds at Pending Prepayment. Carrier and service are mapped to the warehouse's, and customs values go in the order currency, excluding VAT.
Transfers and purchase returns
Transfers in and out of the warehouse location, with shipping details, and purchase returns for the warehouse to pick and send back to the supplier.
Back to Business Central, one posting per event.
Purchase receipts
One receipt per delivery, received on the purchase order and left for your buyers to invoice against the supplier's invoice. A delivery booked in over several rounds is grouped once the order has been quiet for a while, and a later wave on the same order posts as its own receipt.
Over-deliveries follow your policy: raise the line to what arrived, or stop above a tolerance for a buyer to decide.
Sales shipments
Shipped and invoiced in one posting, for exactly what left in that shipment. Weave sets Qty. to Invoice on every line as the last step before posting. Orders marked Combine Shipments are shipped with nothing to invoice, and Business Central's own batch job invoices them.
The tracking number, tracking link and the carrier actually used are written on the order before it posts, so they appear on the posted shipment and invoice.
Customer returns
Returns on a return order, and returns booked back onto the original sales order, are both received and credited in one step at the return order's own price. If no return order exists, Weave creates one from the sale, with the sale's VAT treatment.
The return reason recorded by the warehouse decides where stock lands: sellable stock or your claims location. Return fees come from your table by reason and currency, at most once per return. Credit memos carry the sale's payment method, payment reference and customer, so refunds can be matched.
Transfers
Transfer receipts as goods arrive, one receipt per arrival, and transfer shipments as goods leave, with carrier and tracking.
Purchase returns
Shipped in Business Central when the warehouse sends them. The supplier's credit memo stays with your accounts payable team.
Stock adjustments and claims
Counts and corrections made in the warehouse post to a Business Central item journal, one line per event, every 30 minutes. A move between a shelf and the claims bin becomes a reclassification between your sellable and claims locations.
Once a week, Weave creates and releases one transfer order out of the claims location for what both systems agree sits on the claims bin.
You hear about a problem before a customer does.
Order check
Reopening or deleting a sales order or a transfer out in Business Central asks the warehouse first, live. Once picking has started, a reopen asks the person to confirm and a delete stops with the reason.
If you switch it on, a sales order a person deletes before picking starts is cancelled in the warehouse after one more live check.
Stock comparison
Every night, and whenever you ask, Business Central's stock at the warehouse locations is compared with Ongoing's, per SKU. Picked goods count as still in the warehouse until they ship, and the claims location is compared on its own. Each difference lists the documents since the SKU last agreed.
Oversold
Every 15 minutes, released sales order lines the warehouse says it cannot pick, and released orders it does not hold.
Backlog
Late sales orders, purchase orders gone quiet after a partial receipt, transfers stuck in transit and inbound orders in error, by age against your limits. Owners can be nudged in Slack, with snooze and handled buttons.
Quiet warehouse
A warning when the warehouse books or ships nothing for longer than usual on a working day.
Exceptions, raised once
A condition raises when it is new or comes back after being fixed, and closes itself when a later run fixes it. Each says what it means, why it was raised and what to check. Work that has used up its retries is the only kind that asks a person.
In the words a Business Central consultant would use.
A cursor per feed, advanced last
Weave reads Ongoing's inbound transaction feed, where every event has its own id, with a cursor stored on Weave's side. Each page is stored first and the cursor moved after.
Lot ids and an inclusive fromId
Ongoing's OriginalArticleItemId is a lot id, and its fromId is inclusive. Rows are matched within their lot by content, so a replay inserts nothing.
Windows where there is no id
Shipments and movements are read as overlapping date windows and deduplicated on a natural key. A shipment that changes is kept as a new version.
Per event, never a running total
Each event carries its own quantity, and the Ongoing event id is stamped on the posted receipt line.
Retries return the first document
Posting the same event again returns the original document. A request whose answer never arrived is settled by asking Business Central. Five attempts, then one exception.
The invoice is the event
Weave sets Qty. to Invoice on every line, as the last write before posting, to what this posting moves.
Readers that can only read
The Ongoing read clients send only reads. Every write goes through one file of named operations with its own credential. Weave leaves Ongoing's reported-quantity field to others.
Its own pages in Business Central
Weave's extension publishes API pages with location, variant and return reason, and posting routines that receive, ship and credit per event.
Dry by default
Anything run by hand is a dry run until confirmed, and a production connection needs a second confirmation.
One flow at a time, checked before it counts.
Each flow has its own switch and start time. In shadow, Weave records what it would post and a nightly comparison sets it against what Business Central holds, order by SKU. When a flow matches, switch it on.
Connect
Install the extension, register Weave's Entra application, add the Ongoing credentials.
Shadow
Weave reads both systems and records what it would post.
Compare
The nightly diff shows each order and SKU where the two disagree.
Switch on
Per flow, from a start time you choose. The first documents can be posted by hand and checked.