The Order Queue and CSV Export

The queue

Go to Orders to see your workspace's orders, 25 per page. The queue opens on Open: every order still in the shop's hands (awaiting payment, paid, in production or ready for pickup), oldest first, so the order that has waited longest is at the top. Use the filter tabs to find orders by status:

• Open — Awaiting payment, paid, in production and ready-for-pickup orders, oldest first (the default).
• Awaiting payment — Orders waiting for payment.
• Paid — Paid orders waiting to be stitched.
• In production — Orders being stitched.
• Ready for pickup — Stitched orders waiting for the customer.
• Picked up — Orders the customer has collected.
• Cancelled — Cancelled orders.
• All — Every order regardless of status.

The All tab (and its CSV export) leaves out picked-up and cancelled orders placed more than 90 days ago, and says how many it left out. Nothing is deleted: a search or a date range finds them, and the Picked up and Cancelled tabs still list them.

Dates

Every tab except Open lists newest first. To narrow the list to the days orders were placed, set the two dates beside the search box (Placed from and to; either one on its own works too). Days are your shop's days, in the time zone under your workspace settings (UTC when none is set), and both dates are included. The tab counts are always for all dates. When you open an order, ← Orders takes you back to the same tab, search and dates.

What each order shows

Each order in the queue shows the personalized text and the item, so you can pick the next job without opening it. Orders with a customer comment show a Comment badge and the start of the comment. An order that has been awaiting payment for 7 days or more shows a Stale tag (see Order statuses). Opening an order shows everything to sew it (see Order details).

From a phone. If you let customers order from their own phones (Settings → Kiosk), their orders show a From a phone tag in the queue and on the order page. Nothing is made until they pay at the counter, as with a tablet order.

Team members with the Viewer role see a note that they can view orders but not change them.

Searching

Search matches order number, customer name, email, phone, or receipt token. Phone numbers match however they're formatted (312 555 0105 finds 3125550105), part of a number works too (555-0105 finds +1 312 555 0105), and straight and curly apostrophes match each other (O'Brien finds O’Brien). You can also paste or scan a whole receipt code: the receipt QR code (the customer's proof link) or an older receipt barcode (TR-RECEIPT:…).

Time zones and order numbers

Order numbers (TR-YYYYMMDD-…) carry the date the order was placed in your shop's time zone, or in UTC when no time zone is set.

Every date and time in the app (the order list, the order page and its audit trail, the work order, the dashboard) is in your shop's time zone, so the same order shows the same time everywhere. Set it under Settings → General; a new workspace starts in the time zone of the browser you signed up on, and until one is set times show in UTC. The CSV export keeps exact UTC timestamps, which spreadsheets and other systems read without guessing.

New orders

ThreadReady checks for new orders every 30 seconds on every page of the app, not only the Orders page. A "New order" notification appears when one arrives, with an Open order button; to also hear a chime, open the Scan button in the bottom-right corner and turn on New-order sound (it's also on the scan screen). The choice is kept in this browser, and the chime plays on any page. The Orders item in the top menu shows how many orders are open, and the queue refreshes on its own when orders change — no reload needed.

If your shop has no orders yet, the empty queue tells you to place a test order on your paired kiosk tablet, or links to Settings → Kiosk to pair one first.

Test orders

A test order is a real order you place to try the kiosk and the counter. It stays in Orders with a Test tag, so you can take it through payment and production, but Analytics and the dashboard's Orders placed chart and average order value leave it out.

• From the dashboard. While your shop has no orders, the dashboard's Place a test order opens the kiosk in this browser with a "Test order" notice. The next order placed there is marked as a test, as long as you are still signed in; the order after it is a real one again. Place a real order instead on the notice turns it off. This browser must be a paired kiosk to place the order.
• On the order page. Owners, admins and members can turn Test order on or off in the Order Summary card (for example for a test placed on the counter tablet). The change is logged in the order's audit trail.

The CSV export, the API and webhooks still include test orders, marked with test_order (CSV) or isTest (API and webhooks), so your own systems can leave them out too.

Exporting orders to a spreadsheet

Owners and admins see Export CSV in the Orders page header. It downloads the orders the list is showing: the same tab, search and dates, every page of them, oldest first. An order whose status changes while the file downloads is still listed once, and no other order is skipped. Set the filters first, then press Export CSV. The file opens in Excel, Numbers or Google Sheets and has one row per order with these columns:

• order_number, created_at (when the order was placed) and updated_at, as UTC timestamps
• customer_name, customer_email and customer_phone
• status (the stored value, for example ready_for_production for In production)
• test_order: yes for a test order, otherwise no
• currency, total (the approved price; empty for an order placed while your shop didn't price orders) and line_items (each price line and its amount, separated by ;)
• template_name and receipt_token
• placed_from: kiosk for a shop kiosk, phone for an order a customer placed on their own phone

A cell that a spreadsheet could read as a formula (starting with =, +, - or @) gets a leading ' so it shows as plain text. The export still works while your workspace's billing is paused.

The file holds your customers' contact details, so members and viewers don't see the button and can't download it by URL. Every export is logged with who ran it, when, the filters used and how many orders it held (a shop-wide record, so it doesn't appear on any one order's audit trail).