Start with roles that match the real office
A corporate portal works best when each person sees only the jobs that matter to them. A branch manager may need full ordering rights, while a junior marketer only needs to raise a request and attach artwork. Finance may need visibility on pricing and invoices, but not the ability to alter product details.
For Durban and Johannesburg clients, this matters when several depots share one account. If every user has the same access, one rushed order can override a carefully checked item list, or a trainee can see pricing they should not handle. Clear roles keep the account tidy and reduce accidental changes.
- Ordering role for approved buyers
- Approval role for managers and finance teams
- Read-only role for staff who only need status updates
- Admin role for account owners who manage users and templates
Approval rules that fit corporate buying lines
Approval rules decide when an order stops, and who signs it off before production. Some clients want every order above a set value checked by a manager. Others only want certain products, such as uniforms or sales kits, to trigger approval. The rule should reflect how the company actually spends money, not how the software happens to work.
In a Cape Town head office, a marketing team might place short-run brochure orders directly, while business cards and presentation folders need a second sign-off. That split keeps routine work moving without letting the wrong items slip through. It also gives the print shop a cleaner queue, because urgent jobs do not sit behind every minor request.
- Approval by spend limit
- Approval by product type
- Approval by branch or department
- Approval by named person or group
Product builders need guardrails, not freedom without limits
Product builders help a buyer configure size, paper, finish and quantity without phoning for every detail. That freedom is useful, but it needs guardrails. If a corporate client can enter any size or choose finishes that do not suit the machine setup, the portal creates avoidable admin and wasted proofs.
Good portal controls limit each product to approved options. A Pretoria retailer might allow only standard sizes for point-of-sale posters, with preset paper stocks and finish choices. A branch user then picks from the approved range, and the system calculates the price from the right matrix. This keeps the process clear for the client while protecting the shop floor from odd requests.
Artwork checks should happen before the file reaches the proof queue
Artwork rules are most useful when they catch the obvious problems early. A portal can flag low-resolution files, missing bleed, wrong colour space, or a document that is too small for the requested size. It should also show the buyer what file types are accepted and what the art team expects on each job.
For corporate accounts, the aim is not to be pedantic. It is to save time on fixes that should never reach production. If a Bloemfontein branch uploads a logo on a pale background for a dark substrate, the portal can alert the user before the job moves ahead. That sort of preflight check keeps the process in order and reduces rework.
- File type checks
- Resolution and bleed checks
- Artwork placement rules
- Colour and substrate warnings
Price matrices keep the quoting side honest
Corporate portals often handle repeat work with set pricing rules. That is where price matrices matter. The portal can price by quantity breaks, branch type, substrate, finish or artwork version, depending on how the print shop structures its jobs. The goal is not fancy pricing, just consistent pricing that matches the service sheet.
When a client in Paarl orders the same stationery set each month, the matrix should apply the same logic every time. If the account includes different price bands for different user groups, that can be built in too. The fewer manual edits a team has to make, the less chance there is of a pricing slip that later confuses accounts and production.
Tracking orders through production keeps everyone on the same page
Once a job is approved, the portal should show where it sits in the workflow. Corporate users want to know whether a file is under review, in print, in finishing, packed for courier, or ready for collection. That status trail matters when multiple departments are waiting on one delivery and nobody wants to ring the shop twice for the same answer.
A Durbanville client with several outlets may want each branch to see only its own jobs, while head office sees the full account. Good tracking controls make that possible. The print shop spends less time explaining where things are, and the buyer can check progress without digging through our contact form threads.
- Job status by department or branch
- Proof approved or still pending
- Production stage visibility
- Courier handover and collection notes
Local rollout works best when staff can use it without guessing
In South Africa, corporate portal setups often involve teams across Cape Town, Johannesburg, Durban and Pretoria, with each office handling orders a little differently. That is where staff training matters. The portal should be set up with the people who place orders, the people who approve them, and the people who manage the account. If those groups are trained together, the rules make more sense and the account stays cleaner.
A real example is a company with a head office in Cape Town and branches in Stellenbosch and Bloemfontein. Head office may own the pricing rules, but each branch needs clear ordering rights and visible approval steps. Once the portal reflects that structure, the print shop gets fewer stray requests and the client gets a cleaner paper trail.
At PrintEngine, portal setup usually ties together product templates, user roles, approval steps, artwork rules and order tracking so the whole account behaves in one way. That includes payment settings, delivery options and admin access, with enough control for the client and enough structure for the print shop to run the job properly.
