Find the source
Search existing Shopify customers using store fields or bring a CSV/XLSX file. Keep the original record and source row visible.
COMPANY ONBOARD / SHOPIFY B2B
Prepare existing wholesale customers for native Shopify B2B purchasing. Group companies, locations and buyers; inspect the proposed changes; then verify what Shopify actually records.
Built for Shopify B2B stores. Company and location creation needs a plan with native B2B companies, and every native change is previewed, confirmed and read back.
01 / The task
A customer tag, email or similar company name is a clue, not proof that two buyers belong to the same purchasing organization. Company Onboard keeps the proposed structure visible so a merchant can choose the correct native company, location and contact access.
02 / The workflow
Search existing Shopify customers using store fields or bring a CSV/XLSX file. Keep the original record and source row visible.
Review suggested companies, purchasing locations and buyers. Existing Shopify IDs are reused only when the relationship is confirmed.
Edit the proposed groups and missing fields, preview native changes, then confirm the batch. Conflicts remain visible instead of being silently merged.
Follow the saved task and report. Completed Shopify writes remain in Shopify; paused or uncertain steps need review before continuing.
03 / Clear boundaries
Company Onboard does not import purchase orders or set sales commissions. It does not turn a tag into credit approval, a tax exemption or an eligible catalog. Markets, catalogs, prices, payment terms and purchasing readiness still need separate merchant review in Shopify.
04 / Get a precise answer
The Company Onboard guides explain sources, grouping, review, task recovery and what the app does with merchant data. They are written from the current implementation and its limits.
05 / Questions
Short, checkable answers about sources, imports, safety boundaries and the company workspace. Each one is also published as FAQPage structured data, so a search engine or an assistant reads exactly what you read.
Kaupvik B2B Company Onboard lets merchants filter existing Shopify customers by tags such as wholesale or company: prefixes, or by nested conditions (AND, OR, NOT), group them into native Shopify B2B companies and company locations, preview the hierarchy, and assign Ordering only buyer roles while keeping the original customer identities, tags and order history intact.
Yes. Kaupvik B2B Company Onboard supports uploading UTF-8 CSV or XLSX files of up to 500 rows and 5 MB per batch, with a four-category column mapper for Buyer identity, Company & purchasing access, Location address and Existing business context. Unmapped columns are left unused, and every row can be edited before any native Shopify record is written.
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.
Inside the Companies & locations workspace, merchants can switch between an interactive Relationship map — a tidy layered canvas with Hand pan and zoom, Select drag-to-reorder, per-card collapse and level filters — and a Company tree to organise company profiles (the kaupvik.profile_tags metafield), add purchasing locations, or move buyer location access through a reviewed operation.
A company profile is a grouping label that lives in Kaupvik until you assign it, while a native company is the Shopify record that owns locations, contacts and buyer access. Assigning a profile writes the company metafield kaupvik.profile_tags in a reviewed batch and never renames the company.
Limits: 12 profile tags of up to 50 characters, a public HTTPS logo URL, and up to 50 companies in one reviewed assignment.
Each completed operation is saved, so a paused batch resumes where it stopped and pausing never undoes a native change. If Shopify's response cannot prove whether a write happened, the task stops at Needs result check and asks you to verify the saved intent in Shopify instead of importing the same source again.
There is no automatic rollback: completed native changes stay in Shopify.