Completed sales can remain available for historical queries when a collectible-toy brand changes retail systems. Pre-orders, uncollected purchases and active returns still require fulfilment. Migrating them means preserving payments, stock reservations, loyalty benefits, limited-purchase eligibility and responsibility for the next action—not merely copying an order row.
Before cutover, choose a complete route for each open-transaction category: finish in the old system or continue in the new one. Allowing both systems to modify the same order risks duplicate shipments and refunds, incorrect stock releases, duplicate coupon restoration and wrongly reinstated purchase eligibility.
Identify open orders by their next business action
Status labels alone are unreliable. “Paid” may mean awaiting shipment, while “completed” may still fall within a return period. Find orders requiring shipment, collection, refund, exchange or release of stock and entitlements.
| Order type | Outstanding action | Handover data |
|---|---|---|
| New-product reservation | Arrival notice, balance payment, conversion or cancellation | Deposit, member, item, quantity and expected arrival |
| Limited-release pre-sale | Validate reservation eligibility, limits, consumed eligibility and cancellation rules | Member eligibility, collection store and usage state; restoration follows existing brand rules |
| Pre-order awaiting collection | Verify collection, deduct stock and complete | Amount paid, collection code, store and stock reservation |
| Paid, unshipped order | Pick, ship, confirm delivery or refund | Payment state, outstanding quantity, fulfilment location and delivery information |
| Return or exchange in progress | Inspect goods, refund, exchange and adjust benefits | Original order, returned products, payment evidence and responsible store |
Also record the original order number, member identity, channel, time, current state, completed actions, next action and owner. A total count of pending orders cannot support individual fulfilment.
Assign each category a complete handover route
Legacy completion can suit small numbers of short-lived orders where the old system remains safely accessible. Retain restricted permissions for stores and customer service. Migration is more suitable for long-running orders, large volumes of future collections, imminent legacy retirement or orders whose stock and benefits must be managed centrally in the new system.
Orders completed in the old system must not simultaneously become new reservations or benefit calculations. Migrated orders need traceable references between systems, while the legacy system must stop shipping or refunding them.
Headquarters should approve routes by channel, transaction type and payment method. For example, store pre-sales before a specified date may finish in the old system while later orders move. Apply consistent approved routes within each category. Designated roles must approve exceptions and record them separately.
Hand over orders, stock, payments and benefits together
Pre-orders and collections often reserve stock. Check whether the old system has already reserved it, whether import will reserve it again, and which system releases it on cancellation. Otherwise both systems may consider the same product reserved.
Payment records establish the amount paid and refund responsibility. Whether the new system can refund through the original route depends on the payment provider, original references and interfaces. If it cannot, assign the refund to the old system or original channel and tell store and service teams where to query it and who handles it.
Transfer point deductions, locked coupons, reservation eligibility and limited-event benefits with the order state. Cancellation and return treatment must follow existing brand rules. An amount due alone does not capture entitlement actions already taken.
Control new and changing orders during cutover
Define the last legacy order time, final extraction time, new-system start time and the process for changes between them. Stores and online channels that continue trading need an incremental register of payments, collections, shipments, cancellations and returns after the freeze point.
Set temporary rules for customers arriving to collect or return goods during the freeze. Operations may be deferred, completed in the legacy system or recorded for subsequent entry. Use one approved route per channel and transaction type, with separately approved exceptions. After back-entry, reconcile stock, payments and benefits so temporary records do not become permanent discrepancies.
Run at least one near-full-volume rehearsal using the production order-selection, state-conversion and import rules. Record duration, failures, discrepancy causes and correction versions. The first sample migration refines rules; the final rehearsal tests whether cutover can execute.
Accept the handover through the customer’s next action
Import success proves only that a record exists. Test these subsequent actions:
- Reservations display deposits, outstanding balances and expected products, and can convert or cancel correctly.
- Limited-release pre-sales validate eligibility and purchase limits; cancellation or return preserves or restores eligibility according to brand rules.
- Uncollected pre-orders can verify the customer at the designated store, complete collection and deduct stock.
- Paid, unshipped orders can continue fulfilment with traceable original payment and new-order references.
- Cancellations release reservations and return points or coupons according to policy.
- Active returns link to the original sale and complete inspection, refund and stock-status treatment.
- Freeze-window additions and changes are entered, with no duplicate fulfilment across systems.
Close critical differences before launch. Record affected orders, values, owners and deadlines for other differences and obtain operations, service and relevant business approval. Final handover must not leave unexplained order-state or reservation differences.
Include handover routes in scope and supplier acceptance
The PEKON Smart Retail System covers store POS, orders and inventory, including reservations and pre-sales. Separately classify state mapping, historical-order import, original-route refunds, reservations and external connections as standard functionality, configuration, integration, custom development or unsupported. Pre-sale support does not imply that all legacy orders migrate unchanged.
Use the companion PDQ, complete-box and individual-unit migration guidance for stock commitments, and the member-identity, points and coupon guidance for entitlements. Include handover routes, payment boundaries and volume rehearsals in supplier acceptance.
The open-orders section of the collectible-toy migration checklist can organise legacy-completion and new-system routes. Contact PEKON to clarify pre-sales, collection, limited eligibility and returns.
Frequently asked questions
Should every open order migrate?
No. Short-lived orders can finish in an accessible legacy system. Long-running orders, imminent legacy retirement or unified stock and entitlement management may favour migration. Use an approved route for each channel and category.
Which fields are essential for uncollected pre-orders?
Original order number, member, items and quantities, amount paid, collection code or verification data, collection store, reservations, status and subsequent owner. Limited products also need eligibility, limits and usage state. Confirm payment and fulfilment-specific fields.
Can migrated orders be refunded through the original payment route?
That depends on the provider, payment reference, interfaces and configuration. Otherwise assign the refund to the legacy system or original channel, preserving access and ownership.
When has the handover passed?
Real samples pass eligibility, collection, shipment, cancellation, refund and return tests; incremental changes are entered; and order counts, paid amounts, outstanding quantities, reservations and entitlements have no unexplained differences.