All use cases
Proof of Compliance · Compliance
  1. 01Rules on real steps
  2. 02A history that cannot be edited
  3. 03Audit pack
  4. 04Data protection

The auditor asks: was this checked when the order shipped?

Rules that live in procedures are hard to prove. Otiox runs compliance rules on real steps — confirming and shipping orders, receiving goods — records every check in a history that cannot be edited, and builds the audit pack and data-protection overview an auditor asks for.
app.otiox.comFig. 00
Compliance
Execution history
Chain verified · 9 records
StepRuleOutcome
Shipping a sales orderSwiss notification validPassed
Confirming a sales orderSanctions screeningWould have been blocked
Supplier paymentSupplier payment holdBlocked
What to do

Open any record to see the checks behind it; export the audit pack for the period.

Proof for every step, on demand.

01The Challenge

You did the check. You cannot show it.

Orders ship after a licence check that happens in someone's head. When the auditor asks for proof, there is a spreadsheet, a few e-mails and a lot of goodwill.
  1. 01
    Checks done but not recorded
  2. 02
    Logs that anyone can edit
  3. 03
    Audit packs assembled by hand
  4. 04
    Retention and legal holds unclear
02SEE IT IN OTIOX

The same situation, in the product.

Real screens from the Otiox demo workspace, step by step.
  1. 01

    Rules

    Company rules built from the regulatory list: sanctions screening before every shipment outside the EU (would have refused 3 in 30 days), the Swiss notification for customers in CH and LI, the Reykjavik operating licence when receiving (warn), UKCA for customers in GB, Norwegian producer responsibility — each with its step, place, check and strictness.

    Rules
  2. 02

    Execution history

    Every check on an action — who did it, the outcome, the evidence at that moment: here 9 records, 5 passed, 3 would have been blocked, 1 blocked (a supplier payment hold). The chain verifies; records cannot be changed or deleted.

    Execution history
  3. 03

    Audit pack

    What was on your list for a period, with the official wording as it was then, evidence hashes, licences, deadlines and changes — as PDF and JSON, each pack logged with a hash you can verify later. External auditors get read-only access for a set time, at most 180 days.

    Audit pack
03

How It Works

Purpose-built features that solve these exact problems.
01

Rules on real steps

Conditions on confirming and shipping sales orders, receiving purchase orders and starting production — monitor, warn or block, built from items on your regulatory list.
02

A history that cannot be edited

Every check recorded in a chained history; the chain verifies, and any change would show.
03

Audit pack

The list for a period with the official wording as it was then, evidence hashes, licences, deadlines and changes, as PDF and JSON with a verifiable hash.
04

Data protection

Retention per kind of file, files marked as personal data, and legal holds that stop deletion.
04

What You'll Gain

Tangible improvements that impact your bottom line.
  1. 01
    Proof, not promises

    Each check with its time, outcome and rule.

  2. 02
    Safe rollout

    Rules start by watching before they warn or wait.

  3. 03
    Less audit work

    The pack is built from what is already recorded.

  4. 04
    Retention handled

    Files kept as long as needed, and no longer.

05

Real-World Scenarios

See how this works in practice.
Scenario 1

Sanctions screening before shipping outside the EU

In monitor mode the rule shows it would have refused three sales orders in 30 days — before anyone switches it to block.
Scenario 2

Shipping to customers in Switzerland and Liechtenstein

Each shipment checks that the Swiss hazardous-substances notification is valid that day.
Scenario 3

Products placed on the market in Great Britain

Shipping to GB customers checks that the UKCA file was verified in the last 365 days.
06

The Transformation

From chaos to clarity.
Before
  • Checks in heads
  • Editable logs
  • Audit packs by hand
  • Retention unclear
After
  • Rules on real steps
  • Chained, verifiable history
  • Audit pack on demand
  • Retention and holds set
07

Frequently Asked Questions

Quick answers to common questions.
01Can a rule stop the business?
Only if you choose so. Rules start by watching; warning and waiting are switched on per rule.
02How is the history protected?
Each record is chained to the one before; a verification shows if anything was changed or removed.
03Can auditors look themselves?
Yes: read-only access for a set time, at most 180 days; what they open is logged.
Proof of Compliance

Ready to transform your proof of compliance?

See how Otiox can solve your specific challenges.