Skip to main content
In Nymble Commerce, an Organization is the top-level container for all your data. Every customer account, product, order, invoice, and integration lives inside an organization. Whether you’re a single brand or managing dozens of client accounts, the organization boundary is where Nymble Commerce draws the line between tenants.

​
What is an organization?

Every Nymble Commerce tenant is an organization with a unique OrganizationId. When you authenticate, your JWT carries this identifier automatically — you don’t need to pass it as a query parameter or request body field in most API calls. Nymble Commerce reads it from your token and scopes every read and write to your organization only. Organizations are useful across several deployment patterns:
  • Multi-brand operators — run distinct storefronts under a single Nymble Commerce subscription, each with its own product catalog and customer base.
  • Agencies and platforms — manage multiple client accounts from one place, with complete data isolation between clients.
  • SaaS platforms with tenant isolation — give each of your customers their own scoped environment without building isolation logic yourself.
// Example decoded JWT payload
{
  "sub": "user_abc123",
  "OrganizationId": "org_f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "OrgCode": "acme",
  "PriceTier": "Wholesale",
  "role": "Admin"
}

​
OrgCode vs OrganizationId

Nymble Commerce uses two different organization identifiers for different purposes:
IdentifierFormatPurpose
OrgCodeHuman-readable string (e.g. "acme")Used during login and storefront routing. Customers and reps enter this to identify which organization they belong to.
OrganizationIdUUID (e.g. "org_f47ac10b-...")Internal identifier used in all data relationships. Embedded in your JWT as a claim after authentication.
You supply the OrgCode at login time. From that point on, your JWT carries the OrganizationId and Nymble Commerce uses it automatically. You rarely need to reference OrganizationId directly in your integration code.

​
Data isolation

Every resource in Nymble Commerce is scoped to exactly one organization. The API enforces this at the data layer — not just the application layer — so there is no risk of cross-tenant data leakage. The following resource types are fully isolated per organization:
ResourceIsolated by org?
Products & catalog✅ Yes
Customers & contacts✅ Yes
Orders✅ Yes
Invoices & payments✅ Yes
Documents & reports✅ Yes
Sales reps✅ Yes
Price tiers✅ Yes
Integrations✅ Yes
No API key, user token, or admin credential from one organization can read or write data belonging to another organization.

​
Organization hierarchy

Your organization acts as the root of a tree that all your commerce data hangs from: 
Organization
├── Price Tiers       (e.g. Wholesale, Retail, Distributor)
├── Terms             (e.g. Net30, Net60, COD)
├── Customers
│   ├── Contacts      (primary, billing, shipping contacts)
│   ├── Addresses     (shipping and billing addresses)
│   └── Orders
│       └── Invoices
│           └── Payments
└── Products
    ├── Categories
    └── Price Points  (one per price tier)

​
Organization settings

You can configure the following at the organization level. Changes apply to all users, customers, and API calls within your org.
SettingDescription
Price tiersDefine named tiers (e.g. Wholesale, Retail) that control which prices customers see. Each tier has a name and a CurrencyCode.
Payment termsAdd or remove terms options available when creating orders (e.g. Net30, Net60, COD).
CurrencyEach price tier can be tied to a specific currency code. Customers and orders inherit the appropriate currency from their tier.
IntegrationsConnect payment providers, ERP systems, and other third-party services at the org level.
API accessCreate and manage API keys scoped to your organization for server-to-server integrations.
Customer attributesDefine custom attribute fields that appear on every customer record in your org.
Product attributesDefine custom attribute fields that appear on every product in your org’s catalog.
For full integration configuration details, see the Integrations guide.