The task list
Tasks and reports lists every import batch in a table with the columns Task, Companies / locations / buyers, Progress, Status, Updated and a View task button. The task column is the short task ID — the first eight characters of the batch ID — which is what you quote when you contact support.
The status labels tell you what the app believes:
- Ready for review — the batch is a saved preview with no blocked rows.
- Needs correction — at least one row still has to be fixed.
- Ready to import — confirmed, waiting for the first write.
- Importing — reviewed steps are running.
- Paused — the batch stopped at a safe boundary and can be resumed.
- Needs result check — a write outcome could not be proven from the response.
- Imported · verification pending — the steps finished and the readback has not run yet.
- Import verified — the native identities and roles were read back successfully.
- Selling readiness confirmed — a human completed the selling readiness statement for this batch.
Overview counts the same work in three cards: Migration tasks, Confirmed switches (batches whose profiles and access were verified before switching) and Bulk change history.
Open a row with View task. A running or finished batch keeps a permanent table under Task details · {task ID} · {n}/{m} operations with the columns Operation, Company / location and Status, so you can see exactly which write is done and which is not. Two progress meters track the same run: Import profiles (completed operations) and Verify purchasing access (verified purchasing relationships), summarised as N of M operations complete · X of Y purchasing relationships verified.
Paused and uncertain work
When Shopify clearly rejects a step, the batch pauses with the reason and the failed step stays visible. When the response cannot prove whether a write succeeded, the task asks for a result check: if a new record was involved, paste the created Shopify GID and select Check saved native result. The app matches the saved intent to the native record instead of repeating the write.
A paused batch resumes with Continue import, or Verify imported profiles when every write is complete but the verification pass has not run.
Pause after current operation is the only stop control for an import batch — there is no cancel that removes completed writes. While a batch is importing, keep the page open: each completed operation is saved, so reopening the task continues from that point.
Do not import the same source again as a workaround for an uncertain step. Do not assume an unproven step failed either.
The import report
An open task can download its import report as a CSV file with Download import report. The report is a record of what the batch covered and what the app proved — it is not confirmation that a company can now buy, and it is not an order, invoice or credit document.
From a finished result you can also jump to View company relationships in the workspace, or Open in Shopify for the company itself, and Import another batch to start clean.
Selling readiness is a human statement
After verification, the app offers an optional selling readiness check. It records that you compared catalog prices, currencies, quantity tiers and taxes; reviewed legacy apps, tags, Flow and ERP dependencies; and verified a real test order in the intended purchasing flow, together with Verification notes and responsible person. Only then does the batch show Selling readiness confirmed and the summary line "Selling readiness confirmed."
This is your attestation, not an automated Shopify check. It does not change catalogs, Markets, prices, payment terms or taxes.
Where bulk changes and version history live
Both histories live in Bulk change history, on one page with two tabs:
- Bulk changes — the audit list of organisation edits and bulk name changes made through Company Onboard, with the columns Change, Steps, Status and Updated. Select an entry to review the saved steps again, stop after the current write, cancel remaining steps, or check a native result. The modal titles are Review bulk name changes for a name batch and Review saved changes for an organisation operation.
- Version history — one saved version per finished change, with the native values before and after it (the modal is titled Review saved version, or Review rollback once a rollback has been previewed).
Import batches are not listed here; they live in Tasks and reports.
The audit tab is a history, not an automatic rollback log. Completed access changes and deletions are not undone by closing the task or the tab, and bulk name changes only change names — they do not touch buyer access, catalog pricing, payment terms or taxes.
Version history keeps what each change replaced
Version history has the columns Change, Records, Rollback, Saved and Review. Change uses names such as Record edit, Bulk name changes, Company profile, New company, New purchasing location, Company deletion, Location deletion, Buyer access move, Buyer access removed, Buyer removed, Profile created, Profile renamed, Profile deleted and Rollback.
Select Review on a version to read each record and field, for example Name: Acme → Acme Ltd, the profile tags it added, or the buyer access it moved. Rollback shows Available or Evidence only.
A version marked Available offers Preview rollback. Rolling back is a reviewed change, not an automatic undo:
- The app re-reads Shopify first. If a record changed after that version, it refuses and writes nothing, so a rollback cannot overwrite newer work. Revert the newer change first, or edit the record in Shopify.
- It then shows the exact reversal steps for the records it will restore. Confirm them and save to Shopify; every step is verified by reading the native record back, and the rollback itself becomes a new version marked Rollback.
- A version that deleted a company, a location or a buyer contact is marked Evidence only. Shopify deletions are permanent, so that version records what was removed instead of claiming it can be restored. The same applies to removing a buyer from a company, and to a version that only created an app profile — the app tells you to delete that profile in Companies & locations instead.
- A version that created a company or location is rolled back by deleting that record, which is only offered while the record is still empty. Once it has locations or buyer access, remove those in a reviewed change first.
- Profile names, profile tag assignments and buyer access moves can be rolled back the same way, and a profile rollback changes app data without a native write.
- A version that is itself a rollback cannot be rolled back again: continue the original rollback in Bulk changes.
Nothing is restored on its own. If a rollback is paused or its result is uncertain, open it in Bulk changes and check the native result before starting another one. The list keeps the most recent 100 versions.
Frequently asked questions
Where do I see bulk changes and version history in Company Onboard?
Both are on the Bulk change history page: the Bulk changes tab is the audit list of organisation edits and name changes, and the Version history tab keeps one before-and-after version per finished change with a Review action and a rollback status.
What is the difference between bulk change history and version history?
Bulk changes is an audit list that records what the app did, while Version history stores the native values before and after each change, which is what a reviewed rollback needs. Neither undoes a completed change on its own.
Can Company Onboard roll back a deleted company or location?
No. A version that deleted a company, location or buyer contact is marked Evidence only, because Shopify deletions are permanent; only changes that did not delete a native record can be rolled back through a reviewed, verified plan.
Why did my rollback get refused?
The app re-reads Shopify before every rollback and refuses to write when a record changed after the version was saved, so a rollback can never overwrite newer work — revert or edit the newer change first, then preview the rollback again.
Is an import report proof that a company can now buy?
No. The downloadable import report records what the batch covered and what the app verified, but it is not an order, invoice or credit document and it does not confirm catalogs, prices, payment terms or taxes.