8.6.3 Maintain Mapping Fields and Resolve Queue Conflicts
Open the queue row and read the Conflict Label, Conflict Class, and Retry History before making a correction. If the issue is a product link problem, open the product mapping or item linkage screen and correct the SKU, barcode, or linked ERP item before retrying the import. If the issue is a customer match problem, open the customer mapping screen and link the order to the correct CRM customer record. If the issue is a fulfillment or stock mismatch, review the stock sync detail and confirm the selling branch, item availability, and fulfillment route before retrying. Retry the affected queue record only after the underlying mapping or master-data issue is fixed. Record the correction in rollout or support notes when the same conflict pattern affects more than one order.
Do not use this screen to mark an order as packed, shipped, delivered, or operationally complete. Those status decisions belong to the commercial and warehouse flows after the linked ERP order exists.
PLATFORM WARNING: Do not use repeated imports or repeated manual pulls as a substitute for fixing mapping errors. If the root cause is not corrected first, the queue will refill with the same failures and duplicate-risk grows quickly.