Question
How does an EDI workflow handle advanced shipping notice (ASN) creation by pulling package and tracking details automatically from Microsoft Dynamics 365 Business Central shipping?
EDI Workflow and ASN Integration Behavior
Microsoft Dynamics 365 Business Central does not natively create or send ASNs directly to EDI trading partners. Instead, ASNs are typically generated and transmitted by third-party EDI providers external to Business Central.
EDI providers automatically pull package, tracking, and shipment details from Business Central’s shipping data when integrated properly.
Dynamic Ship supports this integration by supplying detailed package-level information and shipment tracking to partnered EDI providers, enabling automated ASN creation. This process requires the use of an EDI connector configured to extract data from Business Central shipments and transmit it to the trading partner’s system. Thus, ASN creation via EDI relies on external services that integrate with Business Central shipment records rather than native Business Central functions.
How EDI Integration Extracts Business Central Shipping Data
Microsoft Dynamics 365 Business Central does not natively support generating or sending Advanced Shipping Notices (ASNs) directly to trading partners. ASNs typically require dedicated EDI middleware or third-party software to manage electronic document exchanges. Business Central focuses on core shipping and fulfillment tasks, whereas EDI workflows rely on complex communication standards that are better handled by specialized external systems.
Dynamic Ship extends Business Central’s shipping capabilities by providing detailed shipment and package-level information such as tracking numbers, box contents, and routing details.
EDI providers like SPS Commerce, TrueCommerce, or VanTree integrate by retrieving shipment information directly from Dynamic Ship or Business Central through configured connectors. These connectors automatically gather package and tracking data after shipment to generate and transmit compliant ASNs to customers or carriers.
This separation keeps shipping execution within Business Central apart from the electronic transmission of shipping documents, allowing for flexible vendor-specific EDI setups. Because EDI processing happens outside Business Central, organizations must implement and maintain middleware or services to automate ASN creation efficiently from Business Central shipment records.
If shipment details are incomplete or not transmitted correctly, EDI providers cannot generate accurate ASNs. Without a properly configured connector between Business Central and the EDI service, automatic data pulling and ASN creation will not occur.
In scenarios lacking third-party EDI integration, ASN creation must be managed manually outside Business Central. No meaningful edge cases alter this behavior within standard Business Central without integration.
Tools Related to EDI ASN Handling in Business Central Shipping
Dynamic Ship acts as the central shipping management tool within Business Central, capturing detailed package data and tracking information essential for EDI workflows.
It does not generate ASNs itself but provides the data needed.
EDI providers and connectors operate outside Business Central, interfacing with shipment records exported or accessed from Dynamic Ship to create and send ASNs. They automate the exchange of shipping documents according to partner requirements.
Order Fulfillment Worksheet and Warehouse Insight support shipping and warehouse processes but are not involved directly in EDI or ASN creation.