Shoplazza order changes: keep item rows, packing and package tracking connected

Start with an edit that has an operating consequence

Shoplazza’s order-details guidance allows delivery-information edits for orders that have not yet been fulfilled. The page also contains internal notes, tags and an activity timeline. Those store records help review a change; they do not establish that a warehouse already holding an earlier file has received it.

Consider an illustrative address correction after a Guangzhou pick list was approved. The merchant should identify the order, revised address and superseded instruction. The preparation team should confirm whether the parcel is unpicked, packed, labeled or already handed over before the merchant approves the next action.

Keep repeated item rows inside one order

Shoplazza’s export guide documents XLSX order files and an option to include full order details on every item row of a multi-item order. A repeated address or order header may therefore describe another line of the same basket.

Validate a sample containing several products. Use the store and order identity to group its lines, then map each product or variation reference to the merchant SKU, supplier reference and Guangzhou stock code. Preserve the ordered quantity and approved remaining release quantity separately. A repeated header should not create another parcel by itself.

Agree how the selected export scope relates to the release batch. An export of all orders is not permission to prepare every record it contains.

Issue a correction record with a packing decision

Our editorial recommendation is to use a change record that states the old instruction, replacement version and affected quantity. If the merchant requests another variant, confirm the actual store change method and its effect on the order before approving a revised warehouse mapping.

• Item decision: accepted SKU and quantity, plus any units returned to stock.
• Recipient decision: current address version and the affected parcel.
• Packing decision: approved box, insert or bundle version and any required rework.
• Release decision: named approver and acknowledgment from the preparation team.

For a packed parcel, verify the corrected contents and label before resuming work. Keep unresolved choices separate from the approved batch.

Distinguish fulfillment from a tracking correction

Shoplazza’s bulk-shipping guide distinguishes fulfilling unfulfilled items from updating tracking on fulfilled packages. Fulfillment files include order and line-item identifiers; shipment updates identify the package. One order can contain multiple packages.

Return the actual released SKU quantities and parcel references so the store team can use the appropriate workflow. If a tracking number changes, identify the affected package rather than resubmitting the whole order as a new release. Check carrier names or codes against the supported list for the actual tool.

A store update should reflect the agreed dispatch evidence. Label creation and packing completion remain different from carrier handover; assign responsibility for deciding when shipment data is ready to return.

Test one changed order before enlarging the batch

Follow a sample from its original export through correction, revised packing and dispatch return. Confirm that the superseded file cannot authorize another pick and that any remaining lines stay visible. Review outstanding exceptions before the next release.

Start with our Shoplazza versioned handover, order and tracking records and approved packing corrections. Transfer methods, handling scope and shipment acceptance need review for your store and products.

← Back to Blog