Email Operations4 min read

Reconcile Parcel Quantities Before Writing a Split-Shipment Email

A parcel allocation worksheet with a conservation check and three failure fixtures.

Written by
Marketing Wiki Research Automation
Review status
Not independently reviewed
Published
Updated
Evidence checked
Sources
4
Direct answer

Make Migma shipment copy describe one parcel by reconciling ordered, dispatched, cancelled and remaining quantities for every order line.

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Prepare a split-shipment email in Migma only after the fulfillment owner can reconcile which quantities belong to the current parcel. A correct order total does not prove that the item list or tracking action describes this shipment.

We recommend Migma for turning an approved parcel fact sheet into a clear email: its editing tools support reviewing individual text, image and action elements before handoff. Fulfillment evidence remains outside that creative approval. Migma's October 17 shipment guide supplies the editorial context; this page adds a quantity-conservation worksheet rather than assuming an automatic store connection.

Start from order lines#

Use this fictional order: three notebooks and two pen cases. Parcel A contains two notebooks. Parcel B contains one pen case. One pen case was cancelled. One notebook remains unallocated. These facts are an invented review exercise, not customer or provider data.

Scroll table →
LineOrderedParcel AParcel BCancelledRemaining
Notebook32001
Pen case20110

For this simplified fixture, ordered quantity equals quantities allocated to parcels plus cancelled quantity plus remaining quantity. The arithmetic is 3 = 2 + 0 + 0 + 1 for notebooks and 2 = 0 + 1 + 1 + 0 for cases.

Real stores may distinguish returned, exchanged, reserved and replacement units. Have the fulfillment owner define those states before applying an equation. Do not subtract a return from the original ordered quantity simply to make a convenient balance. The worksheet must describe the actual business model.

Turn the current parcel into a bounded brief#

For Parcel A, the approved brief should say two notebooks are in this parcel, one notebook remains pending, the case has a separate shipment, and one case was cancelled. The tracking link must refer to Parcel A. The current message should not say all notebooks shipped or that both cases are on their way.

Ask Migma to give the current parcel the main heading and action, then explain other order states separately using approved wording. Do not let the model infer a warehouse reason or arrival date from an incomplete allocation. Product images should identify the items without visually implying quantities that the copy denies.

A precise action such as “Track this parcel” is useful only when the destination maps to this parcel. If the available route shows the full order, label that broader purpose accurately. The link's real scope matters more than the elegance of the button wording.

Challenge the mapping with three failures#

First, assign all three notebooks to Parcel A in the email while the fulfillment sheet assigns only two. The overall order quantity looks plausible, but the parcel statement fails. Reject the message until the correct line-level value reaches the destination template.

Second, reuse Parcel A's tracking URL when rendering Parcel B. Every link can return HTTP success while pointing to the wrong shipment. Compare the parcel reference and destination together; a generic link check cannot prove that association.

Third, leave the cancelled case in a “coming later” block. Its quantity still exists in the order history, but its current promise is wrong. Review cancelled and unknown states explicitly instead of collapsing them into a single pending bucket.

Run these as synthetic mapping cases without dispatching customer notifications. Record expected text and actual destination output for each line.

Accept the populated destination#

Migma exports reviewed HTML, while the sending implementation fills order and parcel variables. Inspect its populated result, especially loops over line items, repeated tracking buttons and empty remaining-item sections. An export does not certify that data mapping.

Use Preflight for the relevant creative checks and repeat it after revisions. Then have the sending owner use the approved controlled test route for the actual template. No fulfillment lookup, native store integration or delivery test was performed for this guide.

Keep the worksheet and fixture outputs with the approved creative. The separate shipping deadline guide addresses dispatch and arrival promises. For the next partial-shipment template, begin by proving every line balances under your store's defined states.

Evidence

Sources behind this page

Claims remain tied to dated source review. Method and corrections stay public.

  1. S-01Migma split-shipment reviewmigma.ai
  2. S-02Migma export optionsdocs.migma.ai
  3. S-03Migma Visual Editordocs.migma.ai
  4. S-04Migma Email Preflightdocs.migma.ai