Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Proofing module for promotional products wholesalers: virtual proofs, decoration methods and distributor approvals

A proofing module for a promotional products supplier must store one virtual proof per decorated line, location and decoration method, send it to the distributor who relays it to the end client, and hold the order until a recorded approval arrives. Netbase builds that step into the supplier's ordering platform, not as a separate inbox.

Book a solution review See the related solution

By Netbase Web-to-Print and Print Commerce Desk · Reviewed by David (CEO) · Updated · 11 min read

star

This guide is for suppliers and decorators that sell through distributors and still chase proofs by email. The web-to-print platform guide covers the platform choice, the B2B print portal guide covers internal purchase approvals for corporate buyers, and e-commerce development covers the build.

In this guide

What does a proofing module have to do for a promotional products supplier?

In promotional products, the supplier rarely talks to the company whose logo goes on the pen. A distributor places the order, the supplier's art department builds the virtual proof, the distributor forwards it to the end client, and the answer travels back the same way. A proofing module has to make that relay visible and binding.

The module therefore has three jobs: produce a proof specific enough to approve, record who approved which version and when, and stop production until that approval exists. Reminders and comments only support those jobs.

The industry already has a shared vocabulary for this. PromoStandards, which describes itself on its about page as a volunteer-driven not-for-profit that standardizes the flow of information across the promotional products industry, defines web services whose purchase orders can flag a required proof and whose order status can show an order waiting on one. A module that speaks those terms fits the distributor's workflow instead of adding another portal.

What should a virtual proof record hold?

Treat each proof as a record tied to an order line, not as an email attachment. These fields are the minimum:

  • Order line and part

    What it holds
    Product, part or colour, quantity
    Why it matters
    A proof approved for the navy mug must not release the white one
  • Decoration location

    What it holds
    Front, back, wrap, left chest, barrel, cap
    Why it matters
    Each location can carry its own artwork and method
  • Decoration method

    What it holds
    Screen print, pad print, embroidery, laser engraving, full-colour transfer
    Why it matters
    The method decides what the proof can and cannot show
  • Imprint size and colours

    What it holds
    Maximum area, ink or thread colours, colour matches requested
    Why it matters
    Most change requests are about size and colour
  • Artwork version

    What it holds
    The file and revision the proof was built from
    Why it matters
    Production prints from the approved revision, nothing else
  • Proof version and state

    What it holds
    Draft, sent, approved, changes requested, expired
    Why it matters
    The order releases only on an approved state
  • Approver and channel

    What it holds
    Distributor contact, relayed end-client approval, time stamp
    Why it matters
    Disputes are settled by the record, not by memory
  • Sample flag

    What it holds
    Whether a pre-production sample is required
    Why it matters
    Some approvals need a physical piece, not a picture

The PromoStandards Purchase Order specification, as documented by PSRESTful in its Purchase Order 1.0.0 reference, carries several of these ideas: a DigitalProof object with a required flag and the address the digital proof is sent to before production, a preProductionProof flag on a line item, and an artwork type that separates production-ready files from virtual proofs and supplier art templates.

What must the proof show for each decoration method?

A virtual proof is a picture of intent, and each decoration method limits what a picture can promise. The matrix below sets what the proof must show, what only a physical sample settles, and what the proof record must carry.

Method What the virtual proof must show What only a sample settles Data the proof record needs
Screen or pad print Imprint position, size and each spot colour named Exact ink match on a coloured or curved surface Colour list per location, imprint area, number of colours
Embroidery Placement, size and thread colours, with small text flagged Stitch texture and legibility of fine detail Thread colours, a note that the design must be digitised
Laser engraving Placement and size on the actual material Contrast, which depends on the material, not on a colour Material and finish, single-tone marking
Full-colour transfer or digital print Placement, size and a colour-managed preview Colour shift on the real substrate Artwork resolution and colour mode, substrate

So the proof template must change with the method (a colour swatch on a laser-engraving proof promises what the process cannot deliver), and the art department must be able to mark a line "sample required" and hold it until the sample is approved.

How to build the approval relay through distributors

  1. Accept the proof request with the order

    Read the proof-required flag and the proof address, whatever channel the order uses.

  2. Hold the line, not the order

    Put each decorated line into proof hold, so blank or approved lines can still move.

  3. Build the proof from the order data

    Pre-fill product, part, location, method, imprint size and colours from the order, so the art department only places artwork and checks it.

  4. Send one link per proof version

    The distributor approves or requests changes on that page and can forward it to the end client without a login.

  5. Record the relayed answer

    Store who approved, on whose behalf, which version and when; a change request opens a new version and keeps the old one read-only.

  6. Expire and remind

    Set how long a proof stays valid and when reminders go out, because an approval given weeks later may no longer match stock or ship dates.

  7. Release to production from the approved version

    Production receives the approved artwork revision, and the status leaves proof hold automatically.

  8. Report status back to the distributor

    Expose the proof state through the same status the distributor already reads, so they do not need to call.

PromoStandards order status codes cover the hold steps. The Order Status 1.0.0 reference on PSRESTful lists a "Proof Hold" status, where the vendor is awaiting a response to a proof, next to an "Art Hold" status for an order that is still waiting for suitable artwork. Keeping them separate tells a distributor whose move is next.

Clean files come first: the AI preflight guide covers upload checks, and the integrations guide covers how status data reaches other systems.

Where AI fits

AI helps around the proof, not in the approval. A model can place a logo on a product template as a first draft for the art department, read a distributor's change request written as free text and turn it into a list of proposed edits, and draft reminder messages for proofs that are about to expire. The approval stays a recorded human decision, and engineers test the hold rules like any order rule. Netbase works with the major commercial and open-source AI tools and models, chosen per project, and the one delivered AI feature named with a client is 4over4's product-recommendation engine, which is unrelated to proofing.

Proof follow-ups by chat or phone are a separate decision, covered in the AI customer service guide for print orders.

What delivery record exists, and what does not?

Netbase has delivered 50+ custom web-to-print platforms across apparel, packaging, signage, promotional merchandise and corporate B2B portals. Two records are closest to this topic.

  • Deyar Printing & Advertising, a printing, packaging and signage company. Through Printcart, Netbase scoped and built a bilingual web-to-print platform whose print-ready PDF generation includes pre-flight checks and a proof approval step before production; an AI design and pre-press suite is planned as a later phase, not delivered. See the Deyar record.
  • ACT Printing, a custom apparel and print shop. Netbase delivered print location zones with location-bound artwork upload and preview and a production summary per order; B2B accounts, proofs and reorders are planned as a second phase, so they are not delivered scope. See the ACT Printing record.

Netbase has also delivered online designers on client print stores for promotional items such as mugs, badges, embroidered caps and engraved pens; those clients are not named.

What does not exist. No published Netbase record describes a delivered supplier-to-distributor proof relay or a PromoStandards integration. The proof record, method matrix and relay steps in this guide are a design framework, not a measured result, and no figure for approval time or errors avoided is claimed.

Alternatives: which proofing route fits your business?

Route Strength Choose it when
Email proofs with a shared folder Nothing to build Order volume is low and one art lead tracks every approval by hand
A standalone proofing tool Mockups, versions and approvals already built Your products and methods fit its templates and you accept a second system next to your store
The proofing feature of a promo-industry ERP Proofs tied to orders, inventory and invoicing in one place You are replacing your back office anyway and the ERP fits your distributor channels
A proofing module in your own ordering platform Proof record, method rules and holds fitted to your catalogue and distributors Proofs are a daily bottleneck, you sell through your own store or portal, and distributors expect status in their systems

Standalone tools exist for this job. PromoPlus, for example, describes itself on its product page as artwork approval software for promotional products that takes a job from mockup to client approval and production-ready files. Check that a tool exports the approved revision and approval record to your order system.

In Netbase's own delivery, a proofing module is scoped inside a web-to-print or e-commerce engagement rather than sold as a separate product, and most Netbase projects run on fixed-price contracts agreed after discovery.

When should you not build a proofing module?

Do not build one when most orders are reorders of approved artwork, when one distributor sends nearly all your volume and runs approvals in its own system, or when an ERP with proofing built in is about to replace your back office. If artwork usually arrives unusable, fix artwork intake first.

What are the limits of this guide?

  • The record fields and method rules are a starting framework; check them against your own decoration methods and distributor contracts.
  • PromoStandards versions change and suppliers implement them differently; confirm the fields your distributors actually send before mapping to them.

Plan the next step with a Netbase consultant

Frequently asked questions

A virtual proof is a digital image of the decorated product that shows the artwork, its location, size and colours for one decoration method. The distributor and end client approve it before the supplier puts the order into production.

Yes, if each proof version has its own secure link. The distributor opens the link, approves or requests changes, and can forward it to the end client, while the module records who answered for which version.

When the result depends on the physical process rather than the layout, such as an exact ink match on a coloured surface, stitch detail in embroidery or engraving contrast on a new material. Then the line should wait for a pre-production sample.

Next step

Tell us how proofs travel between your art department and your distributors today and where approvals stall, and we will book a solution review to map the proof record, holds and status your platform needs. The web-to-print platform solution shows how Netbase delivers it, and printing and packaging covers the industry view.

AI-enabled ecommerce development for merchants who outgrew templates AI-enabled ecommerce development for merchants who outgrew templates

Netbase provides custom ecommerce development for merchants that have outgrown templates, to turn traffic into orders with less manual work, using AI for search, recommendations and catalog work where it pays. We build on WooCommerce, Magento 2, Laravel and headless stacks; 4over4, whose store gained an AI recommendation engine, reported 82% more revenue within six months.

Learn More
line
Web-to-print platform with AI design assistance, from online design to a print-ready order Web-to-print platform with AI design assistance, from online design to a print-ready order

A web-to-print platform is an online ordering, design and prepress workflow that helps print businesses sell custom products: customers configure, design and approve their order online, AI can suggest layouts and catch artwork problems, and production receives a print-ready file. Netbase has delivered 50+ custom web-to-print platforms across apparel, packaging, signage, promotional merchandise and corporate B2B portals.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase