E-Commerce & CS-Cart Operations

An order can be marked shipped when a label is created, even though the parcel has not been handed to the carrier. Customers may interpret the status as physical dispatch and become concerned when tracking shows no movement. What to check Review status transition rules, label generation timing, fulfillment workflow, carrier scan delay, and the exact...

A product may appear available while add-to-cart fails because of a disabled variant, purchase quantity rule, inventory race, required option, or a script error. Listing availability can be based on different data than cart validation. What to check Reproduce the exact product, variant, quantity, customer group, and storefront. Review product status,...

Tax can change after sign-in because a saved address, customer tax exemption, group setting, or location rule becomes available. The change can be legitimate but should be understandable before the customer submits the order. What to check Compare guest and account address, tax status, customer group, product tax settings, shipping destination, and tax...

A displayed stock quantity can be stale because of cache, warehouse aggregation, product option configuration, or inventory synchronization delay. The cart may use a different availability check than the product page. What to check Compare product and variant inventory, warehouse settings, reservation rules, cache timestamps, and the last...

An order may be marked complete after payment even though picking, packing, shipping, or service delivery remains unfinished. Customers can receive misleading notifications and staff may miss fulfillment work. What to check Review order status mapping, payment callback, fulfillment workflow, notification triggers, and add-on behavior. Compare the order...

A discount may appear in the cart but not on an invoice if order totals, tax allocation, promotion state, or document templates use different data. Customers and finance staff may see inconsistent amounts. What to check Compare cart calculation, stored order totals, invoice template variables, tax and shipping allocation, and status timing. Review...

An order can appear differently to staff and customers if status mappings, language labels, permissions, or storefront cache differ. Payment and fulfillment statuses may also be combined in one view and separated in another. What to check Compare the stored status, admin and customer mappings, notification template, language, permission, and cache....

An order may show duplicate shipping charges when products ship from multiple locations, a promotion adds a second method, or custom logic applies both per-order and per-item costs. What to check Compare cart package grouping, warehouse assignment, shipping methods, product settings, add-on behavior, and final order totals. Test one product, multiple...