Small and medium business | Business Central, N...

Linking internal shipments to purchase orders

(3) Share

Report

Posted on by JB-10121218-0

Hi!

We’re a webshop from the Netherlands looking for some assistance 😊

Current situation

We use a plugin that connects Business Central to our Magento webshop.
Through this integration:

Incoming Magento orders are automatically created as Sales Orders in BC
Product data is pushed from BC to Magento
We work with internal work orders that are printed and used for shipments from our own warehouse — these internal shipments are not linked to any Purchase Orders
Our sales → purchase → shipment → invoice process is automated as far as possible

We have many suppliers whose pricing and stock levels change daily.
All dropshipment items are routed to the cheapest supplier using two custom job queues:

Job Queue 1: Reads the Sales Order lines based on several filters (purchasing code, supplier name, purchase status) and places the items into the Requisition Worksheet.

Job Queue 2 :Checks stock availability and supplier pricing, and applies bundling rules (e.g., if price difference < €30, use one supplier; otherwise split the order).

Tracking automation

Daily, via Power Automate, we receive tracking information from our suppliers.
We match this to the relevant Purchase Orders and store the tracking data in custom fields.
A second Power Automate flow pushes this tracking information to our webshop using Magento’s Shipment APIs.

The problem

Part of our products is shipped from our internal warehouse.
These items are shipped using work orders, not purchase orders.
Just like the dropshipment flow, this internal process is automated using a job queue that prints the work orders, sends them to the warehouse, and posts the shipments to update inventory.
Because these are internal movements, there is no Purchase Order record available where we can store or automate tracking information.
This results in two separate logistics processes:

Dropshipments → linked to Purchase Orders (with tracking)
Internal shipments → work orders only (no place to store tracking info)

Goal / question

Is it possible to let internal warehouse shipments run through, or be based on, the Purchase Order table?
It is important that these new “purchase orders”:

Do not interfere with our actual supplier purchases
Do not create double purchasing or financial postings.

In other words, can internally generated shipment lines be associated with a Purchase Order so that:

Our warehouse can act as a vendor
Tracking information can be stored in the same way as for external suppliers
Automation tools (like Power Automate) only need to monitor one unified set of tables for both external and internal shipments

I've also looked into warehouse warehouse shipments which i could add some custom fields to for our tracking information, but i can't seem to find the right job queues and get them to work. In this situation each sales order would need to have it's own warehouse shipment to write away the tracking information in a usefull manner.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Assisted by AI

OussamaSabbouh 11,017 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

You can’t route internal warehouse shipments through Purchase Orders in standard BC without causing real purchasing/financial postings. PO = vendor transaction, always.

Best approach:

Use Posted Sales Shipment as the single place to store tracking (it already has Package Tracking No. and Shipping Agent fields).

For dropshipments: when supplier tracking arrives, copy it to the Posted Sales Shipment linked to the Sales Order.

For internal shipments: your job queue writes tracking to Posted Sales Shipment after posting.

Power Automate + Magento read from one unified source instead of PO + internal process.

Clean alternative: create a small custom tracking table and write both internal + external tracking into it.

Regards,

Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
JB-10121218-0 8 on at

Like (0)

Report
Copy link

Link copied!

Hi Oussama,

Thank you for the quick response!

I’ve experimented with the Posted Sales Shipments table before, and ran into a few issues:

- These documents are already posted, which means Power Automate cannot update any fields on them.

- The posted sales shipment is only created after the items have already been shipped, so it’s too late in the process for us to store or trigger anything based on tracking information.

Another potential advantage of writing the tracking data to a shared table or to the (unposted) sales shipment would have been that we could then run a Job Queue to automatically ship/invoice the related sales orders once tracking information becomes available. Since once the tracking code exists, we can assume the items have shipped, and the order could be processed further.

Would a (small) custom table be best practice in your opinion? Potentially combined with a custom job queue to ship and invoice sales orders?

Was this reply helpful? Yes No

Join the conversation

Community site session details

Linking internal shipments to purchase orders

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2025 Community Spotlights

Congratulations to the January Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Linking internal shipments to purchase orders

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2025 Community Spotlights

Congratulations to the January Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates