Customer groups are the buckets you put customers in to give them a discount, or to limit which categories they can see. Import your customers afterwards and you can put them in a group by name.
Commands
Command
Description
Behaviour
NEW
Create a new group.
Fails if a group with the same name already exists.
UPDATE
Update an existing group.
Uses Group ID if given, otherwise finds the group by name. Fails if there is none.
MERGE
Create or update.
The default. Updates the group if the name exists, creates it otherwise.
DELETE
Delete a group.
Uses Group ID if given, otherwise finds it by name. Customers in it are left without a group.
REPLACE
Refused for groups.
Fails the row. Re-creating a group would give it a new id and move every customer out of it. Use UPDATE.
IGNORE
Skip this row.
Does nothing, and is recorded as skipped rather than as a success.
Category access
Category Access
Means
Category IDs
all
The group can see every category. This is the default for a new group.
One discount per row. A group can hold several discount rules in BigCommerce, but a row describes one. If a group you export has more than one, the export says so in its warning and writes the first — so nothing disappears without you being told.
specific needs its ids. Setting Category Access to specific without Category IDs fails the row rather than quietly hiding every category from the group.
Deleting a group leaves its customers behind. They are not deleted; they simply end up in no group.
Blank cells never overwrite. Leaving Discount Method out keeps whatever discount the group already has — it does not clear it.
A duplicate name names the clash. BigCommerce reports which existing group holds the name, so the failure says which one rather than just refusing.
Amounts come back padded. BigCommerce reports a discount amount as 10.0000; the export trims it, so a round trip does not turn 10 into 10.0000.
Check before you run. The file check flags any column that would be ignored, and a dry run previews every row without writing anything.