Not interested transaction import profile

The Not Interested Transaction import profile lets you bulk-import bill and line-item data for transactions from customers who aren't part of your loyalty program, such as walk-in shoppers with no loyalty enrollment and no customer identifier. Use it to keep a record of this activity in the Capillary database, for example, to measure loyalty program penetration or to identify prospects for enrollment campaigns.

Note: A not interested bill has no customer reference. The profile stores only bill and line-item data. No loyalty points, promotions, or customer records are created or affected.

Note: This profile doesn't support currency conversion. Amounts are stored as provided in your source data.

Who can use this


Audience	Customer Success Manager, brand admin
Access	Self-serve
Product	Capillary Data Platform - Data Import

Before you begin

Till or store codes used in your source data must already be configured for your organization.
Identify which method you need: Insert to load new not interested bills, or Update to correct a bad import (see Correcting a bad import).

Source data format

Your Databricks source table can combine bill-level and line-item-level fields in a single row per line item. Standard fields come first, followed by any extended field or custom field columns for the bill and the line item.

Standard fields

Field	Display name	Required	Description
`till_code`	Till code	Yes	The till or store code where the transaction happened. Must match a till code configured for your organization.
`bill_date`	Bill date	Yes	The date of the transaction. Must fall between January 1, 1995 and today.
`bill_amount`	Bill amount	Yes	The total bill amount. Must be a valid number.
`item_code`	Item code	Yes	The product or SKU code for the line item.
`outlier_status`	Outlier status	No	Leave blank on insert; the system sets this to `NORMAL`. Set to `DELETED` only when using Update to correct a bad import.

All other bill fields, line-item fields, and extended or custom field columns are optional. Include the columns your organization needs; leave the rest out of your source table.

Create an import job

Creating a not interested transaction import job follows the same wizard as other Data Import profiles. For Step 1: Job settings (job type, schedule, approval thresholds, and notifications) and Step 2: Data to import, see Creating an import job. The steps below cover what's specific to this profile.

Step 3: Profile and method

Under Import profile, select Not Interested Transaction.
Under Import method, select one:
- Insert: loads new not interested bills.
- Update: changes the Outlier status field on an existing bill. No other field can be updated through this profile.
Note: Upsert isn't available for this profile.
No additional configuration is needed for this profile. The Additional configurations section doesn't appear for Not Interested Transaction, regardless of the method you select.

Step 4: Fields mapping

Map the mandatory fields: Till code, Bill date, Bill amount, and Item code. The mandatory fields banner shows your mapping progress.
Map any optional bill, line-item, extended field, or custom field columns your source table includes.
If you selected Update, also map Outlier status and set its value to DELETED for the bills you want to remove. Leave every other field mapped the same as your original import; only Outlier status is changed.

Step 5: Review and proceed

Review your configuration summary and field mapping, then select Proceed to validate. The system validates every row before writing valid records to the database.

Correcting a bad import

Because you can't update bill or line-item details after a not interested bill is imported, use this two-step pattern to correct a bad import:

Run an Update job. Map only the mandatory fields plus Outlier status, and set Outlier status to DELETED for the affected bills.
Run a new Insert job with the corrected data.

The corrected bill gets a new, separate record. The original bill is kept with Outlier status set to DELETED for audit purposes, and it's excluded from any line-item association or reporting going forward.

Note: This profile currently supports updating only the Outlier status field. If you need to correct other bill or line-item data, use the delete-and-reimport pattern above rather than a direct update.

Validation errors

Error message	What it means	How to fix
`till_code is mandatory`	The `till_code` column is empty.	Add a valid till code for every row.
`till_code is invalid`	The till code doesn't match one configured for your organization.	Correct the till code, or confirm it's configured for your organization.
`bill_date is mandatory`	The `bill_date` column is empty.	Add a bill date for every row.
`bill_date is not a valid date`	The `bill_date` value doesn't match the expected date format.	Correct the date format.
`bill_date is out of range`	The bill date is before January 1, 1995 or after today.	Correct the bill date.
`bill_amount is mandatory`	The `bill_amount` column is empty.	Add a numeric bill amount for every row.
`bill_amount is not a number`	The `bill_amount` value isn't a valid number.	Correct the value.
`item_code is mandatory`	The `item_code` column is empty.	Add an item code for every row.
`outlier_status is invalid`	The `outlier_status` value isn't a recognized status.	Use `NORMAL` or `DELETED`, or leave the column blank on insert.

FAQs

Can I update the bill amount or other details on a not interested bill after it's imported?
Not yet. This profile currently supports updating only the Outlier status field. To correct other data, delete the bill and reimport it with the corrected values. See Correcting a bad import.

Can I import currency-converted amounts for not interested bills?
No, this profile doesn't support currency conversion. Amounts are stored exactly as provided in your source data.

Do I need a customer identifier to use this profile?
No. Not interested bills have no customer reference by design. If you have transaction data tied to a known customer, use the regular transaction import profile instead.

Updated 4 days ago

Did this page help you?