Use the operational record to read the business.
Garmenly reports on workload, production time, revenue, agents and payments from the same activity that moves garments through the business.
Review workload and production time
Use workload reporting to understand what is waiting, what is moving and where capacity is being used. Cleaning and pressing time provide a practical view of production activity, while alteration operations contribute their configured bench minutes. Review this before offering unusually tight promises.
- Look for work accumulating at a particular production step.
- Compare cleaning and pressing time with the volume being accepted.
- Review alteration bench load before confirming express work.
- Use garment-level scan history when a queue needs investigation.
Compare revenue by site and trade
Revenue can be reviewed by site and by trade, helping you separate cleaning from alterations rather than treating every order as one undifferentiated total. Choose comparable date ranges and confirm whether the report is intended to guide a daily operating decision or a longer management review.
| Question | Useful view | Follow-up |
|---|---|---|
| Which location is producing revenue? | Revenue by site. | Check the transfer and collection pattern behind a change. |
| Is alteration work growing? | Revenue by trade. | Review bench minutes and fitting capacity with it. |
| Are price changes behaving as expected? | Comparable period by trade and site. | Confirm operational changes did not distort the comparison. |
Measure agent-sourced work
Agent-sourced share shows the contribution of the agency network to your work. Read it alongside agent commission and the factory workload the work creates. A higher share can be valuable, but it still requires the production capacity to meet the due dates being promised.
Reconcile payments and variance
Payment reconciliation compares the recorded payment activity with your expected takings and shows a variance where they do not agree. Reconcile regularly while the counter team can still remember a refund, correction or unusual transaction. Use the original order and payment records to resolve a variance.
Choose the correct trading period and site
Do not combine locations or days unless that is how your physical takings are actually counted.
Compare recorded payments to expected takings
Review the variance, not just the total, so small differences are not carried forward unnoticed.
Check exceptions against source records
Look for refunds, corrected payments, terminal outcomes and orders completed at another site.
Record the explanation
Keep a clear operational explanation with the reconciliation process so the owner can review it later.
Prepare onboarding CSV imports
Customer records, price lists and alteration operations can be imported from CSV during onboarding. Prepare separate, tidy files with one row per record. Use operation names staff recognise, prices that are current, and estimated bench minutes that reflect the work you want the due-date engine to allow.
- Customers: remove obvious duplicates and keep contact details in the correct columns.
- Price lists: use current service names and final prices.
- Alterations: include the group, operation, price and estimated bench minutes.
- Curtains: state the per-metre pricing convention clearly.
Export your data
Your data can be fully exported at any time. Plan the export around the question you need answered, preserve the original file and restrict access to people who should handle customer and business information. Australian hosting is the default, with regional hosting available for UK, US and Canadian customers.
Related articles
Still need a hand?
Email support with the report, period and site you are reviewing. We can help you locate the operational record behind the number.