Ecommerce operations
The supplier portal: let suppliers do the data entry, keep the approval
The most expensive part of a large catalogue is not the platform. It is the person retyping supplier spreadsheets, chasing images at the wrong resolution, and guessing at dimensions. The supplier portal moves that work back to the party who already has the data, without giving them the keys to your live catalogue.
GoGee feature series · 19 of 33
How it's actually built
- Supplier record
- Name, slug, contact details and an active flag
- Supplier logins
- Separate supplier user accounts, not admin accounts
- Supplier screens
- Login, products, bulk upload, bulk images, settings
- Admin screens
- Suppliers, supplier reviews, supplier emailers
- Submission tracking
- Import batches with draft, submitted, applied, failed or cancelled status
- Row-level detail
- Raw and normalised data per row, plus how it was matched
- Product linkage
- Supplier ID, cost price, tax class, digital and backorder flags on the product
- Review record
- Supplier review audit of approval decisions
- 01Input
Supplier record
Name, slug, contact details and an active flag
- 02Deterministic
Supplier logins
Separate supplier user accounts, not admin accounts
- 03Deterministic
Supplier screens
Login, products, bulk upload, bulk images, settings
- 04Deterministic
Admin screens
Suppliers, supplier reviews, supplier emailers
- 05Output
Submission tracking
Import batches with draft, submitted, applied, failed or cancelled status
Supplier portal, data flow, generated from the shared GoGee feature diagram template.
Suppliers log in to their own portal
Suppliers get their own accounts and their own screens: their product list, a bulk upload, a bulk image upload and their settings. They never see another supplier's catalogue, your margins or your customers.
Products carry the supplier reference along with the commercial fields you would not want in a supplier's hands to edit freely, cost price, tax class, digital and backorder flags.
Everything arrives as a batch you review
An upload becomes an import batch with a status of draft, submitted, applied, failed or cancelled. Each row keeps its raw values, the normalised values the platform derived, and how it was matched to an existing product. Nothing is written into the live catalogue until it is applied.
That is the whole point of the design: the supplier does the typing, your team does the approving, and the approval decisions are recorded in a supplier review audit rather than lost in email.
- Raw and normalised values kept side by side, so a bad unit conversion is visible
- Match type recorded per row, you can see what it attached to before you approve
- Batches can be cancelled without touching live product data
Images are treated as a separate queue
Image submissions have their own upload path and their own store, so a supplier can send imagery for products that already exist without resubmitting the whole product record. Supplier emailer templates handle the chasing when a submission is incomplete.
Questions we get asked
Can a supplier change live prices on my site?
No. Supplier submissions land in a batch with a status and are only written to the catalogue when your team applies them.
Can suppliers see each other's products?
No. Suppliers log in to their own portal scoped to their own records.
Is there a record of who approved what?
Yes, approvals are captured in a supplier review audit.
Read next
Operations
CSV bulk upload, everything
GoGee's bulk import maps messy CSV and Excel headers to catalogue fields, converts money to cents and units to…
Ecommerce operations
Product feeds for Google & Meta
GoGee generates Google Shopping and Meta product feeds as XML or CSV per branch, logs every run with included …
Ecommerce operations
Enterprise ecommerce ops
Inside GoGee's operational layer: capacity-based delivery slots, shipping zones and rate bands, business accou…

