Manager controls · action-specific evidence

Know who changed what—and keep exceptions beside the sale.

Authorized users can filter supported administrative action records by action type and review the actor, entity, details, and time. Transaction detail separately retains supported refund, price-override, and age-check context beside the original sale.

Two records · one accountable operation

Start with the action, then open the record that owns it.

The visual below uses supported field names, not fictional employee or merchant activity.

ADMINISTRATIVE ACTIONPermission-gated history
  1. ActorAuthorized user
  2. ActionSupported action type
  3. EntityAffected record
  4. DetailsAction-specific context
  5. TimeRecorded timestamp
TRANSACTION DETAILException beside the sale
  1. RefundReason · operator · time · amount
  2. Price overridePermitted line context
  3. Age-checkSupported outcome
  4. Original saleItem · tender · employee

LiftedPOS provides action-specific operational evidence. Not every system event is represented, and the product record is not by itself sufficient for a legal or regulatory audit.

LiftedPOS transaction history used to inspect the sale and supported exception context
Real product proof · transaction history is the starting point for supported sale and exception detail.

Manager outcome

Investigate the exception without separating it from the work.

01

Review supported administrative actions

Authorized users can filter the history by supported action type and inspect the actor, entity, details, and time attached to the entry.

02

Keep refund accountability with the sale

Supported transaction detail can retain refund reason, operator, time, amount, and original transaction context.

03

Read checkout exceptions deliberately

Permitted line-price override records and supported age-check outcomes remain transaction context rather than being mislabeled as the administrative history.

Manager FAQ

Know which evidence LiftedPOS can show.

Who can review the administrative action history?

Authorized users with the required administrative permission can review supported action records and filter them by supported action type.

Which fields appear in the administrative action view?

Supported entries can show the actor, action, entity, details, and time. The exact record depends on the action that produced it.

How is transaction accountability different?

Transaction detail is a separate operating record. It can retain supported refund reason, operator, time and amount, permitted line-price override context, and age-check outcome beside the original sale.

Is the action history a complete legal audit?

It is action-specific operational evidence. Not every system event is represented, and the product record is not by itself a legal or regulatory audit.

See the capability inside a working store.

Run it with safe demo data, then map the locations, roles, devices, and configuration your operation needs.