Just upload a CSV from the admin to create, suspend, and reactivate staff accounts all at once. PIN assignment for POS staff can be included in the same upload.
Create admin and POS staff accounts in one go. POS staff can be created with a PIN already assigned.
Suspend existing users in bulk — fast, accurate offboarding when someone leaves or a contract ends.
Bring previously suspended users back in bulk. No need to recreate accounts for staff returning for peak season.
| Item | Traditional | CSV import |
|---|---|---|
| Account creation | One at a time Enter each one individually in the admin | Bulk List the rows in a CSV and upload |
| POS staff PINs | Set individually | Bulk Created with PINs already assigned |
| Suspend | One at a time | Bulk |
| Reactivate | One at a time | Bulk |
| Mixing creation, suspension, and reactivation | Each one a separate task | Can be combined into a single upload |
| Entry point | Individual actions from Settings > Users | Settings > Users > Import |
The article names these three by name, all moments when a large number of staff changes have to be made quickly and accurately.
Spin up short-term staff for the busy season all at once, then suspend them all at once when the season ends.
When opening a new location and staff count ramps up in stages, you can issue all the accounts in one go before opening day.
Cut off access quickly and accurately when someone leaves or a contract ends, lowering the risk of missing an account.
Open Settings > Users > Import in the Shopify admin.
Download the sample template from the same screen and check the expected format.
Write rows for create, suspend, and reactivate, then upload them all at once.
Questions that always come up when evaluating a feature, but that this announcement doesn't answer. Don't guess — treat them as unconfirmed and verify in the admin or the Help Center.
There's no statement about which plans it's available on, or whether it's limited to certain regions.
Required fields, how to specify permissions (roles), and the maximum number of records per file are all left unstated.
Whether one bad row halts the whole import, whether partial success is possible, and whether there's a rollback are all unclear.
There's no mention of whether this import can be triggered from the Admin API or a webhook. It's presented purely as an admin feature.
The announcement covers only three operations: create / suspend / reactivate. Bulk account deletion isn't addressed.
How bulk-created accounts are notified, and how PINs get to the individual staff members, aren't described.
The design handles create / suspend / reactivate in a single upload. That implies each CSV row has a column indicating the operation type. Confirm the actual column name in the sample template (the announcement doesn't state it).
Being able to bulk-create accounts with PINs already assigned means thatthe CSV itself becomes a file containing credentials. Decide the handling rules up front: don't leave it sitting in a shared drive or chat, delete it after upload, and so on.
Being able to cut off departed staff members' access in bulk meansit becomes easier to explain in internal controls and audits. If you move toward a workflow that exports a CSV from your HR system's list of departures, you can drive the delay in cutting off access close to zero.
The only thing documented is the admin flow (Settings > Users > Import).There is no mention of importing via the API. If you're designing an HR system integration, scope it on the assumption of "automate up to generating the CSV, upload by hand" first.
Since suspensions also run in bulk, getting a row wrong couldlock out your active staff all at once. The article doesn't say whether errors result in partial success or a rollback, sofirst check the behavior with a 2–3 row CSVbefore running your real volume. If you have a development store, validate there first.