Product Configuration

Puzzle Orders Stuck in Inventory Check Due to Incorrect Supplier Inventory Source

Uppdaterad

UPDATE:

Further conversation to continue during business hours Monday. Next updates on Monday.

Uppdaterad

UPDATE:

Teams are further investigating and discussing any potential mitigations. Nothing definitive decided. Next update when a mitigation has been determined or in max 4 hours.

Uppdaterad

UPDATE:

The configuration suggestion has been shared with the customer team to address the issue affecting the 14 orders stuck in InventoryCheck. We are currently awaiting confirmation from their side after they review and attempt the suggested change. Further updates will be shared once we receive their response or max in 6 hours.

Uppdaterad

UPDATE:

CT has given Printdeal a configuration suggestion that should resolve the issue holding these 14 orders. Next update when Printdeal is back in business hours and have tried this containment.

Uppdaterad

UPDATE:

Internal discussions are ongoing on the proposed fix. Further updates will be shared once the internal assessment is completed and a feasible path forward is identified. Next update in max 4 hours or sooner.

Utreder

New Incident: CTIM-2420
Priority: Low
Escalation sent to: PCD: Garuda Squad for review.
Printdeal reported that puzzle product orders are incorrectly entering the InventoryCheck stage because the system is polling inventory data from the wrong supplier. Instead of retrieving stock levels from Araprint, the system is pulling inventory from another supplier (Technotape), causing the website to incorrectly display the product as out of stock.
As a result, orders are being held in processing while waiting for inventory validation. Approximately 14 orders are currently stuck, and new orders continue to enter the InventoryCheck state despite production confirming that sufficient stock is available.
The Garuda team has been engaged to investigate the incorrect supplier inventory mapping and identify the cause of the misconfiguration. Since the issue is not currently critical, it is being tracked through escalation while teams continue the investigation. Next update when we have more details or max in 4 hours.