Points Import
Points Import
Points Import lets program administrators award or adjust member point balances in bulk using CSV files. Each import runs as a batch: you name the batch, upload rows, review how they match existing members, then allocate points so transactions appear on member accounts.
Use batches for periodic accruals (sales results, training credits, contest payouts). For one member at a time, use Add points / Subtract points on the member profile instead (see Single-member adjustments).
Overview
From Rewards → Points Import you can:
- Create import batches with a name, member-facing note, and data type
- Upload a CSV and map columns to member fields and point amounts
- Quality-check each row as Matched or Unmatched before allocating
- Edit or delete rows in a pending batch (until allocation completes)
- Allocate matched rows to member balances in one step
- Review completed batches — allocation is locked after completion
The screen has one tab: Points Import Batches.
Where to find it
- Route:
/points/{programId} - Side navigation: Rewards → Points Import
Prerequisites
- An open program with program administrator access
- Editor role (or higher) — required to create batches, upload CSVs, allocate points, and delete open batches; Observer can view the batch list
- Members on file with Data Keys set — each CSV row matches a member by Data Key (the same field as Data Key on the member profile)
- Members should be Active (or at least exist in the program) before you allocate; unmatched rows do not credit anyone
For member setup and Data Keys, see Members. For automated point awards outside the admin, see the Points API.
Batch statuses
| Status | Meaning |
|---|---|
| Open | Batch created; no CSV uploaded yet (or saved without file data) |
| Pending | CSV uploaded; you can review, edit rows, and allocate |
| Completed | Points allocated — batch name, note, and rows are read-only; batch cannot be deleted |
CSV format
Required and optional columns
When you upload, map your spreadsheet columns to Incentable fields:
| Field | Required? | Purpose |
|---|---|---|
| Data Key | Yes | Must match the member’s Data Key (accountKey) for the row to allocate |
| Points | Yes | Point amount for that member |
| First Name | Optional | Shown in the review table only |
| Last Name | Optional | Shown in the review table only |
| Optional | Shown in the review table only |
Matching uses Data Key only. Name and email columns help you verify the right people before allocating but do not drive matching.
Point values
| Value | Effect on allocation |
|---|---|
| Positive number | Adds points to the matched member |
| Negative number | Subtracts points from the matched member |
| Non-numeric text | Row is flagged; omitted when you allocate unless you fix the value first |
Download Download CSV Template inside a batch for an example file (First Name, Last Name, Data Key, Points).
Step-by-step
Create a batch
- Open Rewards → Points Import.
- Click new.
- Enter:
- Batch Name — must be unique across batches in the program
- Note on transaction (shown to members) — appears on each member’s transaction history for this batch
- Data Type — choose Member for standard bulk member point awards (see Data type)
- Click Save. The dialog closes and the batch appears in the list with status Open.
Upload points file
- Click the batch name (or Edit from the row menu) to open the batch.
- Click Add Points File.
- Step 1 — Select CSV & Map Columns: choose your file and map columns. Data Key and Points are required.
- Step 2 — Preview & Save: review parsed rows, then click add to batch.
Status changes to Pending and the review table appears.
Review quality and totals
After upload, each row shows a Quality Check:
| Quality Check | Meaning |
|---|---|
| Matched | Data Key found on an existing member |
| Unmatched | No member with that Data Key — no points allocated for that row |
Summary totals appear on the batch:
- Total Points in CSV Uploaded — sum of all point values in the file
- Points Matched — sum for matched rows only (what allocation will apply, excluding invalid point text)
- Points Unmatched — sum for unmatched rows (informational; those points are not awarded)
Use Search and Filter By Quality Check (Matched / Unmatched) to focus on problems before allocating.
If any rows have text in the Points column, an alert offers filter for these records so you can fix or remove them.
Edit rows before allocating
While status is Pending (not Completed):
- Use the row Actions menu → Edit or Delete.
- Click Save on the batch to persist changes.
allocate batch to members is disabled while unsaved changes remain (Save first).
You cannot edit or delete rows after allocation.
Allocate points
- Confirm Points Matched and the Note are correct.
- Click allocate batch to members.
- Review Confirm Points Allocation — batch name, note, and point totals (including any rows that will be omitted due to invalid points).
- Click Allocate Batch Points.
On success, status becomes Completed. Each matched row with valid numeric points creates a transaction on the member account:
- Description: Batch
- Notes: your batch note (visible to the member)
- Type: Award
Unmatched rows and rows with non-numeric points are skipped.
Delete a batch
From the batch list Actions menu → Delete (only when status is not Completed). Completed batches remain as an audit record.
Data type: Member vs Company
When creating a batch, Data Type offers Member or Company. Choose Member for typical bulk point awards.
Rows are always matched to members by Data Key, regardless of data type. The Company option is stored on the batch but does not match company records or credit companies directly. Include each recipient’s member Data Key in your CSV.
Single-member adjustments
For ad hoc changes to one person, open Members → Members, edit the member, and use the points section:
- add points — positive adjustment with a note
- subtract points — deduction with a note
Those transactions are separate from import batches but appear in the same member transaction history.
Tips and limitations
- Data Keys first — Import or add members and set Data Key before running a batch. Unmatched rows are the most common failure mode.
- Unique batch names — Duplicate batch names are rejected on create or rename.
- Save before allocate — The allocate button stays disabled until pending edits are saved.
- Negative points — Use negative values in the CSV to subtract points from matched members (same confirmation flow as awards).
- Completed is final — Allocation cannot be undone from the batch screen; use a new batch or single-member adjustments if you need to correct balances.
- Editor required — Observers can browse batches but cannot upload, edit, allocate, or delete.
- Demo programs — CSV upload, template download, save, allocate, and delete are disabled on demo programs.
- Not the same as member import — Members CSV import creates or updates member records; Points Import only changes point balances for existing members.
Related
- Members — Member records, Data Keys, and per-member point history
- Companies — Optional company records and company Data Keys (separate from points batch matching)
- Rewards Catalog — Rewards members redeem after they have points
- Orders — Fulfillment after redemption
- Points API — Programmatic balance and award endpoints
- Dashboard — Program metrics including points activity
