Skip to contentv0.1.0
PIMgate
PORTALS · SUPPLIER2026

Supplier data that arrives clean.

Your suppliers get their own portal with clear attribute specifications per category, validation while they prepare and field-level feedback on every SKU. You review, accept or reject — and only complete, valid records pass the gate into your PIM.

Book a demoSee the quality gate
XLSX · BMECAT · APIFIELD-LEVEL ERRORSSUPPLIERS · UNLIMITED
messara.pimgate.ai / p / supplier / submissionsSupplier
Submission · SUB-2026-0914

messara_q4_catalog.xlsx

In reviewuploaded 2026-09-24 11:07 · 148 rows
Submitted148
Accepted12182%
Held15
Rejected129 fields
SKUProductStatusField error
MS-21004Coupler CO-16Accepted—
MS-21005Coupler CO-20Accepted—
MS-21008Coupler CO-25Rejectedean invalid
MS-21011Adapter AD-12Heldprice above tolerance
MS-21014Adapter AD-16Rejectedcountry_of_origin missing
MS-21020Manifold MF-04Accepted—
MS-21023Manifold MF-06Rejectedunit not in UN/ECE list
MS-21031Sealing kit SK-2Heldawaiting datasheet

Showing 8 of 148 · validated against channel schema v12

The Supplier Portal ships in 2026. Book a demo to see the workflow and plan your supplier onboarding.

01 · Today

Every supplier file is a small project.

01

Specs by email.

Attribute requirements live in a PDF or an old spreadsheet template. Suppliers guess.

02

Errors found late.

Missing units, wrong EANs, unknown classes surface after upload — or after go-live.

03

All or nothing.

One bad row rejects the whole file. The supplier starts over.

04

Re-typed by hand.

Someone on your team copies Excel into the PIM. Every time, for every update.

02 · Who uses it

Two sides of one submission.

Suppliers and vendors

Submit and maintain their product data for your range, see what is required, and fix issues themselves. No backend access to your PIM.

Category managers and purchasing

Define what each category needs, review held submissions and decide what enters your catalog.

Product data team

Stops re-keying spreadsheets and starts governing rules — once, for every supplier.

03 · The journey

From "resend the file" to "12 SKUs to fix".

Six steps a supplier goes through to get products into your range — and what the Supplier Portal changes at each one.

  1. 01 · ONBOARD

    Learn what data to deliver, in which format, for which category.

    Before

    Attribute requirements sent as PDF or template by email.

    With PIM Gate

    Self-service access and a clear attribute specification per category — required fields, units, allowed values, ETIM class.

    2026

  2. 02 · PREPARE

    Format names, specs, images, EANs and prices to your requirements.

    Before

    Format errors discovered only after submission.

    With PIM Gate

    Live validation against your rules before the final submit.

    2026

  3. 03 · SUBMIT

    Upload a full range or a partial batch.

    Before

    FTP or email, no status, no partial delivery possible.

    With PIM Gate

    Upload via XLSX, BMEcat or API, with partial submission — ready SKUs go in, the rest follows.

    2026

  4. 04 · TRACK

    See which products were accepted, held or rejected.

    Before

    No visibility; follow-up by phone.

    With PIM Gate

    A submission dashboard with status per SKU.

    2026

  5. 05 · CORRECT

    Fix flagged items and send them again.

    Before

    The whole file rejected, no detail on what was wrong.

    With PIM Gate

    Field-level error messages and re-submission of failed SKUs only.

    2026

  6. 06 · MAINTAIN

    Keep data current — new prices, specs, images.

    Before

    The same process from scratch for every update.

    With PIM Gate

    Planned: delta updates that send only what changed, with a history of past submissions.

    ROADMAP

04 · The flow

One loop. Only clean records leave it.

Supplier submission loopA supplier uploads product data, live validation splits it into accepted and held records, field-level errors go back, and only corrected SKUs re-enter the loop.SupplierPIM GateUploadXLSX · BMEcat · APILive validationErrors while typingPartial submitGood rows move onReviewCategory manager248 SKUs submitted36 rows with errorsAccepted · ingested212 SKUs liveRejected36 · field-level errorsWhat the supplier gets backMS-14082 · ean invalidMS-14091 · unit missingMS-14103 · etim class unsetRe-submit failed SKUs onlyNo email threads · no re-uploading the whole file

Validate before submit

Suppliers see errors while preparing, not after you reject the file.

Submit what is ready

Partial submissions let complete SKUs move on while the rest is finished.

Fix only what failed

Rejected SKUs return with field-level reasons; accepted ones stay accepted.

Say once what you need. Per category.

Each supplier sees exactly which attributes each category requires, with units, allowed values and classification. Templates and samples are generated from the same rules your team maintains — so the specification and the validation never drift apart.

  • Required and optional attributes per category.
  • Units, value lists and formats spelled out.
  • Downloadable XLSX template and BMEcat sample per category.
  • Self-service access for invited suppliers — no PIM login.
Say once what you need. Per category.Each supplier sees exactly which attributes each category requires, with units, allowed values and classification. Templates and samples are generated from the same rules your team maintains — so the specification and the validation never drift apart.CATEGORY · HEATING PUMPS · ETIM EC011157ATTRIBUTEUNITRULEHeadmREQUIREDRated powerWREQUIREDEAN / GTIN13 digitsREQUIREDColourvalue listOPTIONALXLSX TEMPLATEBMECAT SAMPLE
2026

Errors show up while the supplier works, not after.

Every record is checked against your validation rules before it is submitted: required fields, units, value ranges, EAN check digits, classification. The same quality gate that protects your channels now protects your PIM on the way in.

  • Checks for required fields, units, allowed values and formats.
  • EAN / GTIN check-digit validation.
  • Classification checked against the allowed ETIM classes.
  • Three clear outcomes: passed, held for review, rejected with reasons.

RULES · REQUIRED / UNIT / RANGE / FORMAT / ETIM CLASS

Errors show up while the supplier works, not after.Every record is checked against your validation rules before it is submitted: required fields, units, value ranges, EAN check digits, classification. The same quality gate that protects your channels now protects your PIM on the way in.SKUEAN / GTINRated powerETIM CLASSMS-12011401234567890145 WEC011157MS-12014401234567891760 WEC011157MS-12088401234567892590 WEC011157CHECK DIGIT INVALIDPASSED · 288HELD · 9REJECTED · 3
LIVE

No supplier ever has 100% on day one.

Suppliers submit the SKUs that are ready and keep working on the rest. You decide the rule: accept partial batches outright, or hold them for review until a completeness threshold is reached.

  • Submit ready SKUs, keep the rest as draft.
  • Configurable completeness threshold per category or supplier.
  • Held submissions wait in your review queue — not in someone's inbox.
No supplier ever has 100% on day one.Suppliers submit the SKUs that are ready and keep working on the rest. You decide the rule: accept partial batches outright, or hold them for review until a completeness threshold is reached.EC01115792 % completeACCEPTEDEC01020380 % completeACCEPTEDEC00004246 % completeHELD FOR REVIEWTHRESHOLD 80 %DRAFT · 54 SKUs
2026

Your team decides what enters the catalog.

Category managers review submissions in one queue, compare submitted values with what is currently in the PIM and accept or reject — per SKU or in bulk. Suppliers are notified of the outcome. Every decision is recorded in the audit log.

  • One review queue across all suppliers.
  • Submitted values compared with current data.
  • Accept or reject per SKU or in bulk, with a reason.
  • Supplier notified; every decision audited.
Your team decides what enters the catalog.Category managers review submissions in one queue, compare submitted values with what is currently in the PIM and accept or reject — per SKU or in bulk. Suppliers are notified of the outcome. Every decision is recorded in the audit log.REVIEW QUEUE · ALL SUPPLIERSGrundfos12 SKUs · 4 FIELDS ≠Wilo38 SKUs · 11 FIELDS ≠KSB5 SKUs · 1 FIELDS ≠SUBMITTED48 W · 8.2 mCURRENT IN PIM45 W · 8.0 mACCEPTREJECTAUDIT LOG · APPEND-ONLY2026-09-24 09:14 · c.mueller · accept · MS-12014 · 2 FIELDS ≠2026-09-24 09:15 · c.mueller · reject · MS-12088 · EAN
2026

Fix twelve SKUs, not the whole file.

When a record fails, the supplier sees which field, which value and which rule — and corrects it in place or in the file. Only failed SKUs go back through the gate; accepted ones are not touched again.

  • Error message per field, with the expected value or format.
  • Correct in place or re-upload.
  • Re-submit failed SKUs only.
Fix twelve SKUs, not the whole file.When a record fails, the supplier sees which field, which value and which rule — and corrects it in place or in the file. Only failed SKUs go back through the gate; accepted ones are not touched again.FILE · 300 SKUs300288IMPORTED✓ · 96 %12BACK TO SUPPLIERwith reason per SKUONLY THESE 12 · NOT THE FILE
2026

Planned: send only what changed.

For ongoing maintenance, the Supplier Portal is planned to accept delta updates — a new price, a changed spec, an updated image — without a full resubmission, and to keep a history of every past submission per supplier.

Planned: send only what changed.For ongoing maintenance, the Supplier Portal is planned to accept delta updates — a new price, a changed spec, an updated image — without a full resubmission, and to keep a history of every past submission per supplier.UPLOAD v1 · 300 ROWS2026-06-02UPLOAD v2 · 300 ROWS2026-09-24DELTA · 7 CHANGED7 changed · validated293 unchangedPLANNED
ROADMAP

05 · Formats

Suppliers deliver the way they already can.

Small suppliers fill in an XLSX template. Established ones send BMEcat, as they already do for wholesale. Suppliers with their own systems connect via API. All three land in the same validation. With the ETIM & BMEcat module, ETIM classes and features become part of the specification — so supplier data arrives classified, not just complete.

XLSXBMEcat 2005ETIMREST API
BMEcat 2005
// BMEcat 2005 · ETIM-9.0 (demo codes)<ARTICLE>  <SUPPLIER_AID>MS-S-40220</SUPPLIER_AID>  <ARTICLE_FEATURES>    <REFERENCE_FEATURE_SYSTEM_NAME>ETIM-9.0</REFERENCE_FEATURE_SYSTEM_NAME>    <REFERENCE_FEATURE_GROUP_ID>EC000000</REFERENCE_FEATURE_GROUP_ID>    <FEATURE><FNAME>EF000000</FNAME><FVALUE>16</FVALUE><FUNIT>bar</FUNIT></FEATURE>  </ARTICLE_FEATURES></ARTICLE>// → VALIDATED · 1 of 1 features mapped

ETIM & BMEcat module →

06 · Capabilities

What ships, and when.

CapabilityStatus
Supplier self-service access (invited suppliers)2026
Attribute specification per category, templates and samples2026
Live validation (required, units, values, formats, EAN, ETIM class)LIVE
Upload via XLSX and BMEcat 20052026
Submission via API2026
Partial / threshold submission2026
Submission dashboard with status per SKU2026
Internal review queue, accept / reject per SKU or in bulk2026
Field-level error messages, re-submit failed SKUs only2026
Audit of every submission and decision2026
ETIM classification in specs (with ETIM & BMEcat module)2026
Delta updates and submission historyROADMAP
Single sign-on for suppliers (OIDC / SAML)ROADMAP

07 · Roles

Who can do what.

Example — configurable per tenant
RoleSee specsUpload & validateSubmitSee own status & errorsReview & decideEdit specs & rulesManage suppliers
Supplier user———
Supplier admin——own users
Category manager——✓ (all)own categories—
Product data admin——✓ (all)

Suppliers see only their own submissions.

08 · Scenarios

The Supplier Portal in context.

ILLUSTRATIVE SCENARIO

The Supplier Portal is a portal module. Version S includes one portal module, M two, L and XL all three. Additional modules €2,400 / year. Suppliers are portal users — unlimited in every version.

See pricing →

09 · FAQ

Questions about the Supplier Portal.

Put a gate between your catalog and chaos.

Book a demoTalk to an architect