Introduction
Use the Points Logs CSV importer when you want to backfill historical loyalty activity into Rivo. This creates transaction history rows (not just a one-time balance adjustment), then recalculates each affected customer’s points or credits balance from that imported history.
This is useful for migrations, historical corrections, and bringing older activity into your current program records.
In migration projects, a backfill means importing older transaction history so customers’ past earning and spending activity appears in Rivo (with historical dates, if provided), instead of starting everyone from today.
Before You Import
Go to Settings > CSV Imports.
Set Data Type to Points Logs.
Click Download Template.
Prepare your CSV using the required format below.
CSV Format
Your file must include:
A customer identifier column:
customer_idoremailA transaction amount column:
points_amountorcredits_amount
Optional columns:
sourcepoints_amountcredits_amountinternal_noteexternal_noteapplied_atapproved_atrevoked_atexpires_atorder_idcustom_action_nameearning_rule_idpoints_purchases_id
Header aliases accepted
The importer accepts common header variants, including:
customer_id,Customer ID,CustomerID,Shopify Customer IDemail,Email,customer_email,Customer Email,Shopify Customer Emailpoints_amount,Points Amountcredits_amount,Credits Amountsource,Sourceinternal_note,Internal Noteexternal_note,External Noteapplied_at,Applied Atapproved_at,Approved Atrevoked_at,Revoked Atexpires_at,Expires Atorder_id,Order ID,points_order_idcustom_action_name,Custom Action Nameearning_rule_id,Earning Rule IDpoints_purchases_id,Points Purchases ID
Amount behavior
Positive values add points or credits.
Negative values deduct points or credits.
Rows where both amounts are zero are skipped.
A row can include both
points_amountandcredits_amount.
Date behavior
If applied_at is missing or invalid, Rivo uses the current timestamp.
If approved_at is missing or invalid, it defaults to the final applied_at value.
Invalid revoked_at or expires_at values are ignored.
Matching and Processing Rules
Use one matching method per file
Do not mix lookup methods in one CSV.
During processing, if a batch includes rows with
customer_id, that batch uses customer ID matching.In those batches, rows without a valid
customer_idcan be skipped even if they include an email.
Best practice: use either customer IDs for all rows, or emails for all rows, so matching behavior stays predictable.
Existing customers only
Rows are imported only when the customer already exists in your store’s Rivo customer records.
Unknown customers are skipped.
Duplicate protection
If you import the same transaction row again (including across separate import runs), duplicate rows are ignored.
To count as the same row, key values must match (customer, source, amounts, notes, action/rule fields, and applied timestamp). If you change any of those values, Rivo treats it as a new transaction.
Upload and Monitor Progress
In Settings > CSV Imports , upload your file in the dropzone.
Rivo queues processing in the background.
Open CSV Import Progress and click View CSV Imports to monitor status.
Possible statuses include Pending , Processing , Completed , Failed , Reverting , Reverted , and Cancelled.
For large files, processing time scales with row count. Typical timing guidance:
Up to 100 rows: a few seconds
101 to 1,000 rows: a few minutes
1,001 to 10,000 rows: up to 20 minutes
10,001 to 100,000 rows: up to an hour
Over 100,000 rows: a few hours
If an import sits in Pending, it is waiting in the background queue before processing starts.
What Happens After Import
After rows are imported:
Transaction history entries are created for matched customers.
Customer balances are recalculated for the affected balance type (points and/or credits).
Imported rows are tagged for traceability so they can be reverted later from CSV Imports history.
Customer-facing message records are not generated by this importer.
What customers and admins will see
In admin, imported transactions appear in customer points/credits history and in the CSV Imports history.
In customer-facing activity history, the customer-facing note uses
external_notewhen you provide one.internal_noteis for internal reference and traceability.Some stores have per-entry visibility controls enabled for points logs. If available in your account, you can hide specific entries from customer view after import.
Revert an Imported File
If you need to roll back a completed import:
Go to Settings > CSV Imports.
Click View CSV Imports.
Find the completed import and click Revert.
This queues a rollback for that import and moves it through Reverting to Reverted status.
If you don’t see a Revert button for an older import, contact support for help.
Common Questions About Actions and Expiry
Can I tie uploaded transactions to a specific earning action?
Yes. In a Points Logs import, you can map transactions to specific activity using the source column, and optionally add custom_action_name and earning_rule_id when needed.
If you only need to change balances (not record a specific action history), use manual balance adjustments instead.
Can monthly uploads use different point or credit amounts per customer?
Yes. Every row can use a different value, including positive and negative amounts.
This works well for partner reports, offline campaigns, and one-off corrections where each customer’s amount is different.
How does expiry work for uploaded transactions vs manual adjustments?
For Points Logs imports, use
expires_atif you want a specific expiry date on each imported row.If
expires_atis blank in a Points Logs import, Rivo does not add an expiry date for that imported row.For manual balance adjustments (single-customer or bulk balance updates), expiry follows your points or credits expiry settings.
For earning-rule activity (like order, birthday, or other configured ways to earn), expiry follows your earning setup and program expiry configuration.
FAQ
Can I import points and credits in one file?
Yes. A row can contain both points_amount and credits_amount.
Will this create new customers from email addresses in my CSV?
No. Only customers that already exist in your Rivo customer records are updated.
What if my source value is blank or not recognized?
Rivo assigns a default import source automatically.
Can I safely retry an import file?
Yes, if the key row values are unchanged.
To avoid accidental duplicates, keep applied_at, amounts, notes, and source values identical when retrying.
Can I upload historical timestamps?
Yes. Use applied_at and approved_at in your CSV when you want historical dates preserved.