n8n / Implementation guide

n8n tier pricing and stock allocation for B2B distributors

B2B Wholesale Distributors can coordinate NetSuite ERP and Shopify Plus through n8n, with Claude helping explain exceptions rather than calculate prices. Contract tiers, currency, unit of measure and available-to-promise inventory require deterministic logic. Publishing a price matrix does not reserve stock, so checkout must still enforce the ERP’s allocation rules.

Tools: n8n; Claude 3.5 Sonnet, NetSuite ERP, Shopify Plus
01

The industry-specific problem

A carton price displayed as an each price can erase margin. Concurrent wholesale orders can also oversell the same stock when a storefront treats the last synchronized inventory count as a reservation.

02

Step-by-step workflow

  1. Read authorized NetSuite contract tiers, item units and available-to-promise values in n8n.
  2. Map ERP customer and item IDs to the approved Shopify Plus B2B catalog setup; verify plan capabilities and integration scopes.
  3. Calculate prices using explicit decimal/minor-unit rules and contract dates, never Claude arithmetic.
  4. Publish versioned catalog changes and reconcile acknowledgments. A supported Claude model can summarize conflicting contract notes; the named Claude 3.5 Sonnet API model is retired.
  5. Reserve or validate stock through the authoritative allocation path at order time, and hold orders when catalog or inventory versions conflict.
03

Visual workflow

NetSuite contracts + ATP → n8n unit/currency mapping → deterministic price version
→ Shopify Plus catalog → order-time ERP allocation → confirm OR stock hold
04

Specific configuration example

This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.

// n8n Code node: USD example, carton-to-each mapping
const item = $json;
if (item.currency !== "USD" || !Number.isInteger(item.carton_price_minor) ||
    !Number.isInteger(item.units_per_carton) || item.units_per_carton <= 0)
  throw new Error("Review currency or unit mapping");
return [{ json: { sku: item.shopify_sku,
  eachPriceMinor: Math.round(item.carton_price_minor / item.units_per_carton),
  catalogVersion: item.contract_version,
  stockReservationRequired: true, erpItemId: item.netsuite_item_id } }];
05

Outcome to measure

Illustrative planning metrics only. Not verified client results.

Measure pricing discrepancies, oversold order lines and margin leakage. Illustratively, preventing ten $75 undercharges protects $750 gross billed value; use actual exceptions to validate the business case.

06

Compared with manual work or other tools

A scheduled CSV can suffice for infrequent tier changes. n8n is stronger for reconciliation and exceptions, but high-throughput allocation may require a dedicated transactional service.

07

Work with Imperio Automation

Ask Imperio to audit your NetSuite-to-Shopify units, contract tiers and stock-reservation path.

Scope this workflow
08

Frequently asked questions

Does an inventory sync reserve units?

No. Order-time reservation or authoritative availability validation is a separate requirement.

Should Claude calculate custom tier prices?

No. Use deterministic contract rules and validated currency arithmetic.

What if the ERP uses cartons and Shopify uses each?

Maintain an explicit conversion and rounding policy with tested item mappings.

09

Technical and regulatory references