Import and mapping

Group companies, locations and buyers

Choose how each source row becomes a company, a purchasing location and reviewed buyer access.

Three different records

A Company is the buying organisation. A Company location is a purchasing unit with its own catalogs, pricing, payment terms and tax context — not a warehouse, and not automatically every shipping address you hold. A Buyer is a Shopify customer linked to the company through a company contact and permitted to purchase for specific locations under a specific role.

Grouping decides how source rows become those three records. It reads like a suggestion engine but it never creates an identity on its own: every grouping you see is a proposal until you confirm the batch.

Identify each company

In the Group step, Identify each company from offers five explicit rules:

  • Company name in the source — rows with the same name group together.
  • A company tag, for example company:Northstar — the prefix is set in Company tag prefix and read from each customer's existing tags.
  • One shared company for this selection — every selected customer goes to a single new company you name in New company name.
  • One company per customer — each customer becomes its own company, for stores where a buying organisation really is one person.
  • An exact customer metafield — you name a customer.metafields.namespace.key field and the app reads that value.

A row whose chosen source value is empty is blocked with a message asking you to choose a company explicitly. If two company tags match one customer, the row is blocked instead of guessing which one wins.

Group purchasing locations by

Group purchasing locations by offers:

  • Same full address within each company
  • One shared location per company
  • One location per customer

Grouping by address needs a real address. A row with no address, and no existing location ID, is blocked until you supply an address or choose an explicit location grouping. When several rows share one location, the app asks for one shipping address for it — pick a source address in Choose one address for this location, type one, or choose Do not set a shipping address yet if the location is not ready to ship.

Reuse an existing company or location

Build destination mapping presents every proposed group under the heading N source relationships, and each one carries a Destination company and a Destination location selector:

  • Create a new Shopify company and Create a new location in this company, with the name fields Company name and Location name
  • Use existing: … to point the group at a company or location already in the store
  • Keep existing: … when the source rows already carry a native ID, so you confirm the current relationship instead of replacing it
  • Load more destination companies and Load more locations for {company} when the record you need is not on the first page

When you are done, Review mapped relationships carries the groups into the review step, where the same records appear with New company / Reuse company and New location / Reuse location badges.

Renaming a company in this step never moves an existing B2B membership: a customer who is already a buyer of another company cannot be reassigned by editing a name, and the app says so next to the selector. That is an access change, and access changes are reviewed in Companies & locations.

What the app checks before it writes

  • One customer cannot be assigned to two companies.
  • Conflicting company or location values inside one group are blocked.
  • Conflicting customer names or emails across rows for the same identity are blocked.
  • Two different roles for the same customer and location are blocked.
  • An existing location ID requires its parent company ID, and every native ID must be a complete Shopify GID.
  • Grouping keys use 1–64 letters, numbers, dots, dashes or underscores; entered names and address fields are limited to 255 characters.

Names, tags, email domains and addresses can suggest a match. They do not prove it, so existing native records are reused only after the app revalidates identity and membership. One customer cannot be written into two companies: the row stays blocked until you decide which company is right.

Roles are reviewed per location

Buyer roles belong to a company location. Ordering only is the default role shown on every buyer line in the review tree, and a contact being first in a file is not a reason to grant more. A row can name an optional role GID, which appears as Selected Shopify role; extra approvers and elevated roles have to be configured deliberately. If a re-read finds a role that is not the approved Ordering only role, the batch refuses to adopt it instead of inheriting elevated permissions.

Selling setup is a note, not a switch

The Group step can also carry a selling setup plan — Intended B2B market (planning note), Intended catalog / product selection (planning note) and the legacy pricing, currency or workflow you want to compare. It is collected under the disclosure Complete the B2B selling setup, which also offers Open Markets, Open Catalogs and Open Products so you can check the real configuration in Shopify. Those notes travel with the task and appear again in Review under Selling setup plan · configure separately in Shopify. They assign nothing.

If two buyers in one shared destination disagree about the address, the app does not pick one: it asks you to choose a single Shipping address for this shared location or to group by address instead, and states that the original customer addresses stay unchanged.

Review and confirm an import covers what you confirm before any Shopify write.

Frequently asked questions

Does grouping create companies automatically?

No. Grouping only proposes companies, purchasing locations and buyer access from the rows you selected or uploaded; nothing is written to Shopify until you review the batch and confirm the import, and native records are reused only after the app revalidates them.

Can one Shopify customer belong to two companies?

No. Company Onboard blocks a row that would write one customer into two companies, and an existing membership cannot be moved by editing a company name — moving buyer access is a reviewed change in Companies & locations.

What is the difference between a company and a company location?

A company is the buying organisation, while a company location is a purchasing unit inside it with its own catalogs, pricing, payment terms and tax context — it is a buying context, not a warehouse or a copy of every shipping address you hold.

Which buyer role does a Company Onboard import grant?

Ordering only is the default and only role granted automatically, and any other role must be named deliberately through a Shopify role ID and is reviewed before the batch runs.