The review step is read-only
Review shows what the batch would do, grouped as a tree: each company labelled New company or Reuse company, the locations under it labelled New location or Reuse location, and each buyer line labelled Existing customer or New customer with Ordering only or Selected Shopify role. Counts above the tree summarise how many companies, locations and buyers the batch covers. Nothing is written to Shopify from this step, and you can leave the batch saved and come back to it.
The card also reminds you that one confirmation imports the entire batch, and that existing customer identities, tags and order history are preserved.
Two tabs sit above the content: Review for the tree and Edit for the row table. Use Edit to change the proposed values that belong to this app — a new company or location name, grouping keys, an existing record ID you are confirming — and to correct the source rows that caused a block. Rows with problems are listed with a warning banner: Correct the marked rows in the table. Import will validate the edited batch again before making changes. Existing Shopify names are never changed quietly by an import.
The Edit tab is a working table, not just a list. View filters it to All source rows, Needs grouping, Existing customers or New customers; Search and filter narrows by text; Sort by orders by Original source order, Company name or Newest source row first; and Displayed columns chooses whether Company, Location and Tags are shown. Review & edit row opens a drawer with the same four field categories, each counting how many fields are filled, and the changes apply to this review only — importing the batch is what updates Shopify. Remove selected from source takes rows out of the batch entirely instead of leaving them blocked. When the app detected conflicting source values, the drawer asks you to confirm I reviewed the source conflict and confirmed these explicit groups before the row can proceed.
Rows are blocked for concrete reasons, for example:
- a missing street address or country code for a location that should have a shipping address
- an empty grouping value, or two company tags matching the same customer
- an existing GID that is not a complete Shopify company, location, role or customer ID
- one customer assigned to two companies, or one email with two external keys
- conflicting roles for the same customer and location
- a customer who already belongs to another company
A batch with any blocked row is shown as Needs correction; a clean saved batch is Ready for review. Reopen a saved preview rather than trusting an old one: the app revalidates rows against current Shopify records before it executes anything.
Planning notes are not assignments
The review step also holds optional planning notes — intended B2B market, intended catalog and the legacy pricing, currency or workflow you want to compare. They appear under Selling setup plan · configure separately in Shopify and stay with the task for your own reference. They do not assign a market, a catalog or a price list, and they do not grant credit, tax exemption or payment terms.
The import card says the same thing in one line: prices, catalogs, payment terms and tax exemptions are not granted by this import.
Confirm one batch deliberately
Import reviewed profiles saves the reviewed rows, confirms the batch and then executes the reviewed steps one at a time. Progress counts completed operations, not an estimate. Two things are worth holding on to:
- Keep the page open while the batch runs. Each completed operation is saved, so reopening the task lets you continue — the resume button reads Continue import, or Verify imported profiles once every write is done.
- Pause after current operation stops at a safe boundary. Pausing preserves completed changes; it does not undo them.
When the steps finish, the app runs a verification pass over the purchasing relationships and reports how many were verified. Only then is the batch eligible for the selling readiness check described in Understand tasks, reports and change history. A finished batch shows Import complete. Shopify company, location and buyer access have been verified. with View company relationships, Open in Shopify, Import another batch and Download import report.
If a result is uncertain
If Shopify clearly rejects a step, the batch pauses with a reason and you can correct it. If the network response cannot prove whether a write happened, the task moves to Needs result check and stops writing.
For that case the task shows A write outcome needs checking. Completed operations will not be repeated. Inspect the saved intent before continuing. If a new record was involved, paste its Shopify GID into Created Shopify GID, if this was a new record and select Check saved native result. The app matches the saved intent to the native record instead of repeating the write.
Completed native changes stay in Shopify even if later steps pause, and there is no automatic rollback.
Frequently asked questions
Does importing B2B companies overwrite existing customer order history or grant net terms automatically?
No. Kaupvik B2B Company Onboard enforces strict safety boundaries: Shopify remains the single source of truth, original customer records and historical orders are preserved, and grouping or profile tags never silently grant catalogs, custom pricing, credit limits, net terms or tax exemptions. Every batch requires explicit preview confirmation and post-import read-back verification.
What does confirming an import actually write to Shopify?
A confirmed batch creates or reuses the reviewed companies, company locations and buyer access — buyer contacts with the Ordering only role unless a Shopify role ID was named — and then reads the native records back to verify them.
Can I undo an import after it has finished?
No. There is no automatic rollback for an import: completed native changes stay in Shopify even if a later step pauses, and a paused batch preserves what was already written. Correcting an imported record is a separate reviewed operation in Companies & locations.
Why is my batch marked Needs correction?
A batch is marked Needs correction when at least one row is blocked — for example a missing street address or country code, an empty grouping value, an incomplete Shopify GID, one customer assigned to two companies, or a buyer who already belongs to another company. Fix the rows in the Edit tab and the app validates them again before making changes.
What happens if Shopify's response does not prove a write succeeded?
The task stops writing and moves to Needs result check; paste the created Shopify GID if a new record was involved and select Check saved native result so the app matches the saved intent to the native record instead of importing the same source again.