Start with the portal map before any build
A B2B portal needs a clear map of who logs in, what they may see and which buying rules apply. If that is loose, staff end up correcting orders by hand and clients lose confidence in the portal. Begin with the client groups, the branches they may buy from, and the product ranges that belong in each view.
For most print shops, the first split is between public storefront items and private contract items. From there, add the client team roles, the approval chain, and whether branch managers can place orders for their own sites. A useful portal does not try to show everything. It shows the right things to the right people, with the right controls behind each line.
- List the client companies that need private access.
- Define who may order, who may approve, and who may only view.
- Decide which branches, depots or sites can use the portal.
- Separate contract items from standard catalogue items.
- Set the range of products that each portal should expose.
Roles that keep the ordering process tidy
Role design is where many portals either stay useful or become messy. A finance user may need invoices and order history, while a marketing contact only needs artwork approval and product selection. A branch buyer should not see internal pricing notes meant for head office staff, and a checker should not be able to place orders outside their remit.
Keep the role names plain so client teams understand them without a long explanation. In a Durban or Pretoria group, for example, the same company may need regional buyers, one central approver and a finance viewer with no ordering rights. That structure avoids overlap and cuts down on wrong selections.
- Buyer: can place orders from approved ranges.
- Approver: can release artwork and sign off order details.
- Finance viewer: can see invoices, status and history.
- Branch admin: can manage local users and local delivery notes.
- Portal manager: can update contacts, limits and stored preferences.
Approved ranges and price matrices work together
Private portals usually rely on approved ranges, pricing rules and user groups all working at once. If the pricing matrix is open-ended, users can wander into lines that were never meant for the contract. If the range is too narrow, they end up phoning the print shop for items that should have been easy to order online.
The cleaner approach is to tie each product builder to an approved list, then attach the correct pricing matrix to that list. A corporate client in Cape Town may see one set of branded stationery, while a group with branches in Johannesburg and Bloemfontein may see different print runs, different finishing options and separate delivery choices. It is all about making the portal reflect the commercial agreement already in place.
- Match each product builder to a contract range.
- Hide lines that are not part of the agreement.
- Use quantity bands for clear price steps.
- Set branch-specific or company-wide price rules where needed.
- Check that delivery and collection choices fit the account setup.
Artwork rules should block avoidable mistakes
Artwork upload and proofing are not only production tasks, they are portal structure tasks too. A private client often wants staff to upload logos, select a format and receive proofing prompts before an order moves forward. If the rules are vague, incorrect artwork slips through and the production team loses time on avoidable fixes.
Strong artwork rules should check file type, size, colour mode and page count where that matters. They should also decide who receives the proof, whether approval is required on every order, and when a repeat job can skip a full round of sign-off. In practice, this keeps the portal useful for both the client and the print shop.
- Set file checks for format, dimensions and image quality.
- Require proofing on items where layout changes can affect print.
- Define who gets the proof notice for each portal role.
- Keep reprints and repeats on the same rule set where suitable.
- Record approved artwork against the order history.
Branch controls and delivery logic for South African accounts
Branch control matters when one company orders for several locations. A portal for a retail group in Durban, Cape Town and Stellenbosch should not force every order through one generic delivery route. The structure must allow local recipients, site codes and branch-level delivery instructions while still keeping head office in control of spend.
Courier integration and delivery settings belong inside the portal plan from the start. If a branch can collect, receive by road freight or use a set delivery address, those options should appear only where they make sense. The same applies to payment rules. Some accounts need invoice terms, some need card payment for smaller jobs and others need mixed controls across branches.
- Assign delivery addresses to the correct branch or region.
- Keep collection options visible only where they are allowed.
- Map payment methods to account rules and order size.
- Allow head office to review branch activity where needed.
- Store branch notes for access, unloading or site contact details.
Training the client team so the portal stays in shape
A portal does not stay tidy by itself. The team using it needs to know how to add users, move an order through approval, update a branch note and spot a bad file before it reaches production. Training should cover the practical jobs that happen every week, not only the first login.
When we structure a B2B portal for a print shop, we also plan the admin side. That includes who edits product ranges, who changes pricing bands, who reviews failed artwork and who handles portal support inside the client company. A short handover may cover the basics, but a working portal needs staff who know the moving parts.
- Show each role what they can see and change.
- Train admins to manage users and portal settings.
- Cover order tracking, proofs and re-order habits.
- Document the approval route for common job types.
- Review the structure after the first live orders.
A useful portal checklist before launch
Before a private portal goes live, walk through the structure as if you were the client. Can the right branch log in, see the right products, approve the right artwork and place the right order without seeing unrelated items? If any of those answers are unclear, the portal still needs work.
It helps to test the portal with one company, one branch and one product line before opening the wider account. That gives the team a clear view of missing rules, awkward labels and delivery settings that need adjustment. Once the structure is right, the client side feels orderly and the production side has fewer surprises.
- Check roles, ranges and pricing against the contract.
- Test proofing and artwork upload on a sample job.
- Check branch access and delivery settings.
- Confirm order tracking, payment and invoice visibility.
- Review the portal with the client before broad rollout.
