By default it is the standard Business Central packing list, printed when the shipment is posted. Dynamic Ship does not replace that document. What it adds is the internal package label, which by default is configured as a packing slip for the individual box or pallet, so a multi-box shipment can carry a document describing the contents of each box rather than one document for the whole order.
Order Level and Box Level Documents
These two documents answer different questions. The Business Central packing list covers the shipment as a whole and is the document the customer’s receiving office generally reconciles against. The box level packing slip covers one package, and it matters when a shipment arrives as several boxes that are opened by different people, at different times, or in different departments. The internal package label is a report you configure, so the same mechanism can produce a box level packing slip, a compliance label, or your own address label depending on what the layout contains.
Because packages in Dynamic Ship are real records with known contents, weights, and dimensions, a box level document is accurate rather than estimated. This is especially true when packing is done by scanning items into each box, since the packed contents were physically verified as they went in.
Where the Automation Decision Sits
There are two natural points to automate, and they are separate settings. The first is label printing. If the shipping station uses a cloud print connection, the carrier label goes straight to the shipping printer the moment the carrier and service are chosen, with no print preview and no user interaction. The second is posting. Getting the label and posting the shipment can be configured as one step, in which case posting and the resulting packing list follow automatically, or as two steps, where the shipper reviews the label first and then posts. Two steps is a common preference because it leaves a checkpoint before the transaction is committed.
Choose based on how much variability the station handles. A high volume parcel operation shipping predictable orders benefits from combining the steps. A station handling mixed freight and parcel work, with exceptions and carrier decisions made at the desk, usually benefits from keeping the review step.
A Note on Enforcing Packing Instructions
A related question comes up alongside this one: can the system require that packing instructions, such as using foam or void fill, were actually followed? Dynamic Ship displays packing comments and instructions on the Package Worksheet, so the packer sees them, but it does not enforce confirmation. Where confirmation is a genuine requirement, a pre-shipment checklist through Quality Inspector or a small customization that requires acknowledgment are the two workable routes. The distinction between showing an instruction and enforcing it is worth being clear about during design.
Relevant Tools
Dynamic Ship builds the packages, prints the internal package label as a box level packing slip, and controls whether labeling and posting happen as one step or two.
The PrintNode Connector provides cloud printing so labels and documents route to the correct printer without user interaction.
Quality Inspector supports a pre-shipment checklist where a business needs documented confirmation that packing requirements were met.
The takeaway is that the packing list itself stays native. Dynamic Ship adds package level documents and gives you the setup choices that determine when everything prints, which is usually the real question behind asking where the packing list comes from.