BunStackDocs

Orders

Test orders

Which orders count as test orders, how you mark one, and which reports and figures leave them out.

Last updated · 2 min read

The reports do not count a test order.

Where: Orders › an order › ⋯ Actions.

Which orders are test orders

OrderTest orderThe order page shows
Kustom took payment in the playgroundYes, by itselfPLAYGROUND
Marked with Mark as test orderYesTEST ORDER
Kustom took payment in liveNo. You cannot mark it–
Kustom order without environment details (older orders)No, until you mark it–

The line under the stamp reads, for example, Marked as a test order: left out of OSS, the sales report and Home.

Mark a test order

  1. Open the order.
  2. Press ⋯ Actions › Mark as test order.
  3. Confirm.

The order page now shows TEST ORDER, and Timeline shows the change. ⋯ Actions › Not a test order removes the mark. Both need the admin role.

Where test orders are not counted

  • The OSS report and the destination VAT report
  • Reports and the storefront's Analytics tab, including the test orders' refunds
  • The figures on Home and the storefronts' sales under Storefronts
  • Export CSV from the order list

⋯ › Export CSV with test orders beside the export button includes them. The test_order column is then yes and net empty.

The order stays in the order list, the pack queue and stock as usual. BunStack deducts stock for a test order too.

Go live

The pre-flight check on Go live lists under Test orders the Kustom orders without environment details that are not marked. Mark them or let them count. See The checks before go-live.

See also