Start with the order path, not the software
Before any screens are built, write out the full order path in plain language. Begin where the customer makes a choice, then follow the order through pricing, artwork upload, proofing, payment, production, dispatch and close-out. A good map shows what the customer sees and what your team must do behind the scenes.
For print shops in Cape Town, Johannesburg, Durban, Pretoria and Bloemfontein, the order path often differs by product type. A business card order may need a short form and simple proof. A large-format order may need size checks, substrate choice and delivery notes. Map each product line separately so the setup does not force every job into the same shape.
- List each order entry point.
- Note every approval step.
- Mark where payment is taken.
- Show who releases the job to production.
Build the product flow around real customer decisions
Product builders work best when they mirror how people buy. A customer should be able to choose size, quantity, finish, paper or material and turnaround options without guessing. If a choice affects price, production or delivery, it belongs in the workflow.
Keep the decision tree short where possible. Too many branches make the builder hard to use and harder to maintain. Use clear naming for common products, then separate special runs, bulk orders and custom requests. If your staff still need to explain every option on the phone, the flow is too loose.
Check that every product page has the same basic structure. Customers should know where to upload artwork, where to see proof notes and where to find delivery details. The less hunting there is, the fewer stalled orders you will see later on.
- Define the required fields for each product.
- Mark optional upgrades and extras.
- Set rules for artwork dimensions and bleed.
- Keep our checkout steps in one fixed order.
Set proofing rules before the first job lands
Proofing is where many print workflows slow down. Decide early what must be checked, who checks it and what counts as approval. Some jobs only need an automatic artwork upload and a summary proof, while others need a manual review for layout, trim, spelling or image quality. If that decision is left until later, the team ends up making it case by case.
Write down the proofing route for each product group. For example, a short-run flyer may need a file check and a digital proof, while corporate stationery may need stricter sign-off. Include what happens when the file is missing fonts, the artwork is low resolution or the trim area is unsafe. Those rules protect the team and the customer.
Use one approval language across the full workflow. If the proof is not accepted, the order should not move forward. That sounds strict, but it saves time and avoids confusion on press day.
Map pricing so the quote matches the job
Price matrices are the part most teams underestimate. The workflow must show how price changes when quantity, size, substrate, finishing or delivery changes. A customer should see the right amount before checkout, not after a manual correction from the office.
Write the pricing logic in layers. Start with the base product, then add breaks for quantities, then add rules for extras such as lamination, binding, special cuts or courier delivery. If a product has a minimum run or a price jump at certain quantities, note that clearly in the setup plan.
Good pricing maps also show where staff can override a price and where they cannot. That helps when a corporate client has a custom arrangement or when a repeat order follows a special brief. It also keeps the admin team from guessing which line is active.
- Set base rates by product line.
- Define quantity breaks and minimums.
- Add surcharges for finishing and delivery.
- Record override rules for approved accounts.
Connect payment, delivery and handover to production
Payment and delivery are not separate from the workflow, they finish it. Decide whether an order moves straight into production after payment, or whether certain accounts can be released on terms. If a courier label, delivery address or collection note is needed, make it part of the order record from the start.
Handover to production should be clear enough for the shop floor or finishing team to act without chasing missing details. Include the job number, product type, quantity, file status, proof status and delivery choice in the handover view. That way, the person in production can see what is ready and what still needs attention.
For print shops serving corporate clients across South Africa, this part of the workflow matters a lot. Orders often move between account managers, admin staff and production teams. If the handover is messy, the order slows down long before it reaches press or finishing.
Use one checklist for setup and staff training
A workflow map is most useful when it supports setup and training at the same time. Create one checklist for the client side and one for the internal team. The client checklist covers what they must send, while the staff checklist covers what must be configured before launch.
Staff training should follow the same order as the workflow itself. If the team learns the product builder first, then proofing, then payment and handover, they understand where problems start. If they only see isolated screens, the process feels disconnected.
Use the checklist to test real examples. Try a standard order, a rush order, a custom order and a corporate portal order. See whether every step lands in the right place, with the right notes and the right status. Small gaps show up quickly when the flow is tested from end to end.
- Test the order entry steps.
- Check file upload and proof notes.
- Confirm pricing and payment rules.
- Review production handover fields.
