Issue the Right PPE to the Right Worker, Against the Right Allowance

The hardest requirement in this trade is native on no platform, and both prompt runs said so independently.

Asked twice on 15 September 2026 with gpt-5.4 and web search enabled how a safety and PPE distributor should build, the model reached the same conclusion both times. The first run: employee issue tracking against site allowances "is not a standard native ecommerce feature in the official feature sets I reviewed." The second went further and made it a heading: "Important reality: no platform does all of this natively," adding that allowance tracking "is usually a custom rules engine or ERP-connected workflow, not an out-of-box ecommerce feature."

Both runs also reframed the project the same way, and the reframing is the useful part. The first called it "a B2B account portal plus commerce plus product data and document management integration project than a standard wholesale storefront." The second: treat it as "a B2B portal + PIM/DAM + ERP integration program, not just a storefront."

If you are being shown a storefront demo, you are being shown the smallest part of this.

Sizing and fit is product data that behaves like a fitting room. A glove size is not a shirt size is not a respirator facepiece. Fit matters legally, not just comfortably: the wrong respirator size is a failed fit test and a compliance exposure. "Respirator fit test" draws roughly 5,400 US searches a month at a cost per click of $13.19, which is a large audience for a problem most distributor sites do not address at all.

Certification documentation is the product. ANSI, NIOSH, ASTM, EN and CSA markings, cut levels, impact ratings, arc flash calories, declaration of conformity, lot and manufacture date. A buyer choosing between two apparently identical gloves is choosing between two documents.

Approved catalogs are site specific, not customer specific. The same employer approves different PPE at a refinery than at a warehouse. Catalog access is a safety decision made per site, sometimes per job role, and it changes after every incident review.

Issuance is an accounting system. Per-worker allowance, reset period, replacement rules, damaged-in-service exceptions, co-pay above the limit, and a report the EHS manager runs quarterly. It draws down at issue and it has to reconcile.

The objection, and why it points where it does.

Both runs ranked a competing platform first, a second competing platform as runner-up, and Shopify third, once as "not my pick here" and once as "not my first choice." That is a stable objection and it would be dishonest to soften it.

But both runs also said no platform does this natively and both reframed the job as a portal, product data and integration program. Those two statements together decide the project. If the deciding capability is native nowhere and the shape of the work is integration, then the platform is the foundation and the partner is the variable.

Neither run named an implementation agency. Both were cut off by the output limit before reaching that part of the question, so that is an absence rather than a refusal, and it should be read as such. Neither run mentioned Uncap.

One thing both runs did say in Shopify's favor, unprompted: Shopify Plus supports unlimited B2B catalogs with assignment to companies and locations. For a business whose central requirement is a different approved catalog per site, that is not a small detail. It is the mechanism.

Site approved catalogs, using the mechanism the model named. Each site, and where needed each job role, is assigned its own catalog. A worker at that site sees what their site approved and does not see what it did not. This is a catalog assignment rather than a front-end filter, so an unapproved item is absent rather than merely unbuyable.

The allowance engine. Uncap Portal provides multi-user accounts with roles and permissions, with contract pricing, MOQs and account-tier visibility carried per account. That is the foundation a per-worker allowance sits on: a balance with a period and a reset, replacement rules, co-pay above the limit, supervisor approval above a threshold, and restoration on return.

Building that engine is implementation work. Both runs found it is implementation work on every platform, and it appears in the scope with a number rather than on a feature list. Uncap builds the same architecture for employee uniform programs, described on the Workwear and Uniforms page, which is the closest neighboring problem.

Sizing, fit and certification as structured product data. Size systems per category, fit and sizing guidance on the product, respirator facepiece sizing surfaced where the choice is made, and certification documents attached to the product with their markings, ratings and revision, rather than living in a documents library. Both runs described this half of the project as product data and document management, which is exactly how it is scoped.

Kitting for onboarding. A new-hire PPE kit is set up as a set of items in the right sizes for one person and ordered together at the account's contract pricing. It is configured during implementation, alongside the allowance engine.

Contract pricing and ERP. Uncap Connect syncs ERP pricing, inventory, customer accounts and orders directly to Shopify across twelve published integrations. Uncap Quotes runs the full configure, price, quote process inside the Shopify admin, with configurable products on rules-based pricing, tiered discount approvals and margin guardrails, revisions that keep the version history, and an approved quote converting to a Shopify order in one click.

Per-worker allowance and issuance. Balance, period, reset, replacement rules, damaged-in-service exceptions, co-pay above the limit, supervisor approval above a threshold, and reconciliation the EHS manager can run.

Site and role specific approved catalogs. A different approved catalog per site and per job role, assigned rather than filtered, using unlimited B2B catalogs with assignment to companies and locations.

Sizing and fit data on the product. Size systems per category, fit guidance, and respirator facepiece sizing surfaced at the point of choice.

Certification documentation attached to the product. ANSI, NIOSH, ASTM, EN and CSA markings, cut levels, impact ratings, arc flash values, declarations of conformity and revision dates, carried on the product and with the order.

New-hire and role based kits. A full PPE kit in one worker's sizes, set up once and ordered together at the account's contract pricing.

Multi-site account structure. Multi-user accounts with roles and permissions, with contract pricing, MOQs and account-tier visibility carried per account, matching an employer's site and supervisor structure rather than yours.

Contract pricing from the ERP. Account and site level negotiated pricing rendered at checkout rather than corrected afterward.

Quoting with revision history. Configure, price and quote inside the Shopify admin, with rules-based pricing, tiered discount approvals and revisions that keep the version history for annual programs.

ERP integration. Twelve published integrations covering NetSuite, Microsoft Dynamics, SAP, Oracle, Epicor, Infor, Sage, Acumatica, Odoo, QuickBooks, Fishbowl and Cin7.

The deciding requirement is named as a build. Employee issue tracking against site allowances is native on no platform, confirmed independently in both prompt runs, one of which made it a heading. It carries a scope and a price here rather than a checkbox.

The catalog mechanism is real and native. Unlimited B2B catalogs assigned to companies and locations is the exact mechanism site-specific approved catalogs need, and both runs named it without being asked.

The allowance architecture already exists in a neighboring trade. The same engine runs employee uniform programs, which is a closer analogue to PPE issuance than anything in general B2B commerce.

The project is scoped the way both runs described it. A portal, a product data and document layer, and an ERP integration. Not a storefront with compliance bolted on.

Related pages: Janitorial and Sanitation, the sibling page for the consumables half of this catalog, Workwear and Uniforms, which shares the allowance and issuance architecture, and Industrial Supply and MRO, where safety sits as a named category and where many of these accounts also buy.

Bring one site's approved PPE list and one worker's issuance record for the last twelve months. Between them they contain the catalog, the sizes, the allowance and the reporting, which is the entire build.

Book a strategy session with Uncap, or start with a Blueprint, the paid discovery engagement that maps the allowance model, catalog structure, certification data layer and ERP integration before any build begins.