Demo shop / Check a delivery
Checking graph connection…
SAHIAAYA · MADE FOR SMALL SHOPS

Know what your supplier
still owes you.

See what arrived. Track what’s still owed. Never guess.

SUPPLIER BILL50 billed
YOU RECEIVED48 received
UNACCOUNTED FOR2 units owed
THE NEXT DELIVERY: 2 SOAPS ARRIVE

Which promise did these 2 soaps fulfil?

↳ 2 replacement soaps✳ 2 promotional soaps
Two possible answers. Only evidence can decide.
FICTIONAL DEMO · NOT LIVEThis preview uses fictional data. Live graph and AI investigation require the local Docker app.
01 Check delivery
02 Trace promises
03 Decide safely
▣ TODAY'S DELIVERY TRY THE DEMO

What did you receive?

No signup. Everything in this example is fictional.
SAHIAAYA'S RESULT READY
↗

Let's check your delivery.

Enter the quantities from the supplier's bill and the goods you actually received.

FOLLOW THE EVIDENCE

Why can't we settle both?

Tap a record to see why it matters.

WAITING FOR CASE
Select a record to inspect its evidence and current status.
Interactive fictional example · not real supplier communication
See the proof behind the answerView evidence, graph paths and agent details.
Advanced workspace History · Claims · FalkorDB evidence · Agent
SAHIAAYA · BILL VS BOX · PROMISE VS PROOF

Billed for 50.
Received only 48.

When a shopkeeper receives goods, the supplier's bill and the actual delivery don't always match. SahiAaya finds what's missing and remembers what the supplier still owes—even on the next delivery.

It helps small shops catch shortages, track promised replacements and avoid closing a claim without proof.

A 60-second fictional shop example
WHAT SAHIAAYA DOESFrom checking a bill to closing the missing-goods claim
01
Check the billCompare billed and received
02
Spot what’s missingRecord the supplier’s dues
03
Track the promiseCheck later deliveries
04
Confirm it was fixedClose only proven claims
Demo with fictional information. No real supplier is contacted and no payment is made.
AN EXAMPLE OF WHAT SAHIAAYA DOES

Did the shopkeeper get the missing goods back?

Don’t close either claim yet.

The supplier hasn’t said which of the two promises these soaps fulfil.

What if the supplier says something different? Explore more examples

Same delivery, different supporting evidence.

Missing from previous bill2 soaps still owed
Promised free soaps2 soaps still owed
See how SahiAaya checked this Supplier response · supporting evidence · recorded result
Receipt RCP-52 · SOAP-100G
MERCHANT OBSERVATION

Today’s delivery

Recorded received2
Remaining2
Open promises2
Historical supplier obligations
Evidence-gap agent
REVIEW REQUIRED

What to do next

INVESTIGATING

Reading evidence…

Question to ask

These are simulated replies. A real supplier message and the shopkeeper’s confirmation are required in practice.

0Units reviewed as settled in this scenario
4Units still owed by supplier
Nothing has been settled.

The agent will not turn a plausible allocation into proof.

Try a different delivery Enter your own example · local FalkorDB
NEW · NOT A PRESET SCENARIO

Try your own delivery history.

Enter your own fictional promises and deliveries. SahiAaya builds the graph and works out what is still owed.

LOCAL GRAPH REQUIRED
Local Docker only. No real invoices, names, phone numbers or external communications.
This feature writes synthetic cases to local FalkorDB. On the public Vercel preview, run the Docker version to use it.
WHOLE SUPPLIER LEDGER · FALKORDB algo.maxFlowNOT RUN

What is settled, what is still owed — across every delivery.

In plain words: a delivery is only marked as settling a claim when there is no other possible answer. If two answers both fit the evidence, SahiAaya settles nothing and asks the supplier instead.

FalkorDB runs one max-flow over Delivery → Claim. Then it blocks each link and re-runs it: units that vanish are carried by that link in every valid allocation. Only those forced units are proposed; everything else becomes a supplier question.

–units owed by supplier
–settleable by recorded deliveries
–forced — only one possible answer, safe to propose
–ambiguous — ask supplier
Why did SahiAaya make this decision? View evidence and settlement history
THE CONNECTED EVIDENCE

Why does the decision change?

An invoice and a quantity alone cannot prove which older promise was fulfilled.

EXPLANATION VIEW
Missing supplier attributionThe retailer still has two outstanding obligations.
Evidence trail
CONNECTIONS

Why did SahiAaya decide this?

    Connected evidence pathsFictional preview · evidence from active case
    Select a record to inspect its returned reference.
    Text evidence paths
    Inspect machine decision and graph tool trace
    Reviewed outcome
    AUDIT

    What actually changed?

      No invented recoveries

      No money is shown as saved until a real adjustment is proven.