The customer activation platform.Every interaction becomes a qualified contact. Book a demo

Acceptance policy overview

Understand which receipt checks run before a submission can count in the challenge.

The acceptance policy is the gatekeeper between OCR extraction and reward logic. It decides whether a receipt is eligible to continue based on the data OmniLab could read from the image and the rules you configured for the challenge.

Acceptance policy vs validation policy

These two ideas work together, but they are not the same:

LayerWhat it decidesTypical output
Acceptance PolicyWhether the receipt data satisfies the challenge requirements.Pass or fail
Validation PolicyWhat happens after a compliant receipt passes policy.VALID immediately or PENDING for manual review

A receipt can fail before an operator ever sees it. That is why policy design matters so much.

Where acceptance sits in the status flow

Enough data Unreadable Duplicate Pass + Automatic mode Pass + Manual mode Fail Receipt uploaded OCR reads the image Acceptance policy checks INCOMPLETE DUPLICATE VALID PENDING REJECTED

What the policy can check

In the current receipt-game builder, the Receipt Acceptance Policy screen centers on Field Requirements, with field-specific controls for:

  • Amount
  • Date
  • Merchant
  • Zip Code

Those field requirements can then carry more specific logic, such as minimum and maximum amounts, allowed or restricted merchants, exact-match behavior, and allowed or restricted zip codes.

Depending on the challenge setup, policy validation can also refer to broader receipt checks such as receipt age, submission window, and OCR confidence threshold.

Typical policy design questions

Ask these questions before you touch the toggles:

  • Which fields must always be present for the reward logic to be trustworthy?
  • Is the campaign open to any retailer, or only a partner list?
  • Do you need a spend threshold, a maximum amount cap, or both?
  • Is the challenge local to a store network or geographical area?
  • Should edge cases go to an operator, or should they fail fast?

Example

Suppose the campaign promise is: "Spend at least 25 EUR at participating beauty stores this weekend to unlock a pouch."

A policy that fits that promise usually requires:

  • Amount present, with Min Amount = 25
  • Merchant present, restricted to the partner list
  • Date present, so the challenge can trust the purchase timing
  • optional Zip Code if only some store locations are eligible

What acceptance policy does not do

The acceptance policy does not decide:

  • which reward to unlock
  • how many times a reward can still be won
  • whether operators may force unlock stock later
  • which email template is sent

Those decisions live in challenge rules, winning options, global outcome rules, and notifications.

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page