When a storefront needs hands-on help
Support calls usually start when a shop is checking a template, a price matrix, a proofing step or the handover into production. A small issue in one place can affect the whole order path, so it helps to send the exact product, the screen where it happens, and the kind of job you are trying to run.
If the request is about setup, mention whether you are working on a new product range, a rollout across branches, or a change to an existing workflow. That gives the support team a cleaner view of the issue and avoids back and forth on the basics.
What to include in the support note
Clear notes make it easier to trace the problem across the storefront, the admin area and production flow. A short description is enough, but the right details matter more than a long message.
- The product name or template name
- The step where the issue appears
- Any error text shown on screen
- Whether the order is for retail or B2B use
- Which branch, team or user role is affected
- Whether artwork, pricing or delivery is involved
When artwork is part of the problem, include the file type, page count or trim size if those details are known. If the issue sits in pricing, add the quantity breaks, finish options and any rules that should apply.
Steps for a cleaner support request
Use our contact form and keep the message focused on one issue at a time if possible. That makes it easier to sort whether the fix belongs in a template, a workflow rule, a portal setting or staff training.
- Open the page that is giving trouble
- Note the product or order number
- Describe what you expected to happen
- Describe what happened instead
- Attach a screenshot if the screen shows an error
If the issue affects more than one product, say so. A pricing rule that works on one item may need adjustment across a catalogue, and a proofing rule can behave differently on reprints, artwork replacements or corporate portal orders.
Support for rollout work and live store changes
Some requests are not faults at all, they are part of a rollout. That can include new product builders, a fresh portal for a corporate client, expanded catalogue items, or a review of order tracking and delivery settings. Those jobs usually need a practical look at what is already in place, then a clear list of what should change.
For rollout assistance, it helps to say whether the store is already live or still being prepared. If you are adjusting payment flows, delivery methods or approval steps, mention the teams who touch the process so the change does not break handover in production.
Training follow-up when staff need a reset
Support is often tied to training, especially when a shop is adding new staff or changing how orders move through the system. A short refresher can help with admin tasks, proofing checks, order review and the steps that happen before production starts.
Common follow-up topics include:
- How to read and approve artwork submissions
- How to edit price bands and quantity steps
- How to check portal orders before release
- How to track a job from order to dispatch
- How to manage product templates without breaking the layout
If the team is working across Durbanville, Cape Town, Johannesburg, Pretoria, Durban, Bloemfontein, Stellenbosch or Paarl, it can help to mention which branch needs the refresher.
What the support team can review
The support team can look at storefront behaviour, product setup, workflow logic and the route an order takes after checkout. That includes preflight checks, proofing steps, payment handover, courier selection and the rules that keep a job aligned with production.
If the issue appears only on one browser or one device, say that too. Sometimes the fault sits in a single view of the storefront, not in the whole system, and that detail saves a lot of noise when the problem is traced.
