Supplier inventory CSV import API
supplier_inventory_v1
Import this template via API. Import a supplier catalog from CSV with GTIN, GLN and IBAN validation built in.
30-second curl
curl -X POST https://api.adaptivmapr.com/v1/uploads \ -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \ -F "template=supplier_inventory_v1" \ -F "file=@your_data.csv"
At a glance
- Pack
- Healthcare
- FHIR resource
- —
- Risk level
- low
- Fields
- 5 (2 required, 3 validated)
Why this template?
The Supplier inventory template is the canonical schema for a clinic or hospital's supplier catalogue — SKUs, names, the GTIN that identifies the product to GS1, the GLN that identifies the supplier as a global location, and the IBAN that identifies the bank account you pay them at. Five fields covers the row. The template is `low` risk because suppliers are not patients. Customers use it when onboarding a new procurement system, when consolidating after a group purchasing organisation switch, or when running a quarterly catalog refresh against the latest GS1 directory. The IBAN validator runs mod-97 with a country restriction (CH, LI, DE, FR, IT by default) — fork and extend the country list for cross-border procurement. The cascade catches "référence" and "código" without an LLM call.
GTIN and GLN both run through the same GS1 mod-10 checksum — they share the algorithm because they share the encoding rules. IBAN runs mod-97 in 7-character chunks so the math stays inside JavaScript number precision; this matters because the validator runs in a Cloudflare Worker without BigInt available cheap.
Migration scenarios & common foreign headers
Migration scenarios for Supplier inventory: switching a hospital's procurement system and porting the full vendor master, consolidating after a group-purchasing-organisation change, quarterly catalogue refreshes against the published GS1 directory, and ad-hoc imports for tender comparisons. Foreign headers we see weekly: "SKU / Artikelnummer / Référence / Codice articolo / Código / Bezeichnung / Désignation / Descrizione / GTIN / EAN / Barcode / GLN / Globale Standortnummer / IBAN / Compte bancaire / Konto / Bank Account". The checksum validators are load-bearing — supplier files are notorious for typos and pasted-from-Excel mishaps where a leading zero gets stripped; the GS1 mod-10 catches the corruption before it lands in the procurement database.
Schema
The canonical column set, with the type each row carries, whether it is required, the field-level validators that fire on commit, and the multilingual header hints the cascade resolves against.
| Column | Type | Required | Validators | Hints |
|---|---|---|---|---|
| sku | string | yes | — | sku · artikelnr · référence · codigo |
| name | string | yes | — | — |
| gtin | string | — | gtin | gtin · ean |
| gln | string | — | gln | gln |
| iban | string | — | iban (CH, LI, DE, FR, IT) | iban |
How AdaptivMapr maps your headers to this template
Five layers run in order, cheapest first. Layer 1 (Statistics) auto-accepts headers that have been mapped the same way across past uploads. Layer 2 (Heuristic) compares your header to the column name, the optional label, and every registered hint (DE / FR / IT / EN / ES) after a Unicode-and-punctuation-normalising pass. Layer 3 (Fuzzy) catches typos and reordered words. Layer 4 (Semantic) uses cached embeddings to catch the long tail of paraphrases. Layer 5 (LLM) only fires on genuinely ambiguous columns, constrained to the template’s allowed column set so it cannot invent a field. When a layer auto-accepts, the lower-cost layers below it never run — that is the cost lever.
REST · POST /v1/uploads
Pass the template_id; the cascade picks up the rest.
curl -X POST https://api.adaptivmapr.com/v1/uploads \ -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \ -F "template=supplier_inventory_v1" \ -F "file=@your_data.csv"
The canonical template definition is read-only at GET /v1/templates/supplier_inventory_v1.
MCP · Cursor / Claude Desktop
Drop AdaptivMapr into your IDE. Schema-only calls are free and unlimited.
// In Cursor or Claude Desktop with the AdaptivMapr MCP server installed:
adaptivmapr.match_headers({
template: "supplier_inventory_v1",
headers: ["sku", "name", "gtin", "gln"]
})MCP install instructions →FAQ — Supplier inventory CSV import
How do I add a price column?
Fork the template and add a `price` field with type number. The canonical shape is identifier-focused (SKU / GTIN / GLN / IBAN) because prices change per contract and live elsewhere.
What if my supplier list crosses the IBAN country restriction?
Fork the template and broaden the `countries` array in the IBAN validator. The validator otherwise treats the country as a hard reject.
Does AdaptivMapr verify the GLN against the GS1 registry?
No — only the checksum is verified locally. Registry lookup is a separate, paid GS1 service; we keep the cascade offline-safe.
What about preferred-supplier flags or contract-pricing terms?
Add them via a fork. The canonical row is identifier-shaped (SKU / GTIN / GLN / IBAN) because identifiers are stable; commercial terms shift contract-by-contract and belong in a separate table.