When a student asks whether a piece is ready, the answer should come from a record attached to that piece. A class booking tells you who attended. It does not tell you which shelf holds their bowl or which firing it is waiting for.
Before choosing kiln queue software, define the information the studio needs from intake to collection. Then test whether staff can maintain that record during a normal shift.
Give each piece its own record
Start with an identifier connected to the owner. Add the intake date, the information your kiln team requires, the current location and the next stage.
The exact stages depend on how the studio works. This is a sample record structure, not a firing procedure:
| Stage | Information to record |
|---|---|
| Received | Piece identifier, owner, intake date and required material details |
| Waiting | Next firing or preparation stage and shelf location |
| Assigned to a load | Kiln or load reference |
| Processed | Recorded outcome and the next step |
| Ready for collection | Location, amount due and notification status |
| Collected | Collection date and staff confirmation |
Keep an exception state for pieces that need clarification or cannot proceed. Staff should be able to distinguish a piece waiting for its owner from one waiting for the kiln team.
Choose the physical identification method with the people responsible for firing. A digital identifier is useful only if the team can reliably match it to the object throughout the process.
Decide how charges are calculated
Possible charging models include size, weight, a fixed amount per piece or an allowance within a studio plan. Choose the basis that fits your operation and show customers how the charge is calculated.
Record the measurement or category used. Otherwise staff can apply the same price list differently to similar pieces.
Also define when payment becomes due and what happens if a piece is damaged or cannot be processed. Those are studio policies. The software should preserve the policy and the amount agreed for the piece rather than decide them for you.
Before buying a system, enter several examples from your own price list. Include an exception that normally requires someone to check with the owner. Ask staff to explain each resulting charge.
Make collection part of the workflow
A “ready” notification is only one step. The person handing over the piece needs its location and enough information to identify the owner or authorised collector.
Record collection at handover. If the piece remains on the shelf, its record should remain open. If a customer has several pieces, the system should show which have been collected and which are still in progress.
Choose how you will handle uncollected work and communicate that policy before accepting it. A list of overdue collections can help staff follow up without searching every course roster.
Test the queue with your kiln team
Use a small group of representative records: several pieces from one student, two pieces with similar descriptions, a changed owner contact and a piece that needs an exception.
Move them through the stages your team uses. Change a shelf location and assign a piece to a different load. Then ask another staff member to find the current state without being told what changed.
Check the export as well. It should retain the relationship between the owner, piece, charge and current stage. A list of customer emails cannot reconstruct a kiln queue.
Where Gomry belongs in a pottery studio
Gomry provides booking and payment tools for the teaching side of the studio. Its Experiences product covers scheduled sessions with capacity, and Bundles provide prepaid credits for selected Experiences. Bundles are not a general credit ledger for clay, firing services or one-off Events.
The Subscriptions page, checked on 14 September 2026, describes recurring card billing. Recurring payment alone does not establish support for a measured firing allowance or a piece-level production record.
Gomry does not track individual pieces through the kiln. Keep that record in a system designed for the queue. The broader pottery studio software guide covers the separation between classes, customer bookings and production.
If you want the two systems to exchange information, specify the exact records and updates first. The existence of an API does not establish a ready-made kiln integration. Keep a manual reconciliation process until the required connection has been demonstrated.
Keep booking status and piece status distinct
A student may finish a course while several pieces remain in progress. Cancelling their next class should not close those piece records. Likewise, paying for a session does not prove that any separate firing charge has been paid.
Use a customer identifier to connect the records where possible, while keeping each system's responsibility clear. The event CRM guide explains why purchase, attendance and customer identity should remain distinguishable.
Can a booking system manage the kiln queue?
Only if it also supports the piece records and production stages you need. A roster and a payment list do not provide that by themselves.
Which charging method should the studio use?
Choose a method that the team can apply consistently and customers can understand. Test it against your own range of work; no single method is best for every studio.
Can a Gomry bundle include firing credits?
The published bundle model covers selected Experiences. Do not sell it as a general firing-credit system. Confirm a supported setup before promising any allowance that depends on a piece's measurements or production state.
Begin with the piece currently hardest to locate. If the proposed system lets another staff member find its owner, location, next stage and charge, you have a concrete starting point for evaluating the rest of the queue.