ONE PURCHASE, EXPLAINED

Follow the decision. Keep the record.

A company needs 120 table lamps, with a purchasing limit of €6,000. Follow this example from the first request to the owner’s decision, and see what belongs in the record.

Your company. Your capital. Your decision.

Illustrative walkthrough · Product in development

Scroll to build the example record, or choose a step.

Request

Start with what your company needs.

You tell Operator what you want to buy. The request belongs to your company, with its own budget, destination and purchasing rules.

The buying brief

EXAMPLE

“Find 120 table lamps. Keep the total within €6,000.”

What belongs in the record

  • 120 table lamps and the required specification
  • Delivery destination and timing
  • €6,000 purchasing limit

Does a budget authorise spending?

The limit defines the search. It does not authorise an order or payment. Your company decides how to commit its capital.

Compare

Put the full cost beside the offer.

The example brings the goods price, transport and tax assumptions into one comparison. A public listing is a starting point; availability and terms still need supplier confirmation.

The offer comparison

EXAMPLE

Goods + transport + applicable taxes = the cost to assess

What belongs in the record

  • Listing source and when it was checked
  • Supplier confirmation, when received
  • Transport, taxes and offer validity

What makes the comparison useful?

Sources and assumptions stay beside the prices. A listing is never presented as an agreed supplier offer.

Check

An unanswered question stays visible.

In this example, the delivery terms have not been confirmed. The purchase stays on hold while that open point remains attached to the record.

The open delivery question

EXAMPLE

Delivery terms: confirmation required

What belongs in the record

  • The missing delivery confirmation
  • Who needs to answer
  • The effect on the purchase decision

What happens to the gap?

The record keeps it open. An estimate never silently becomes an agreed delivery commitment.

Decide

The decision stays with your company.

The proposed purchase reaches the owner with its costs and open question. TradeOS is being developed to connect that decision to the company’s agreed authority and limits.

The decision request

EXAMPLE

Owner’s decision required · Delivery terms still open

What belongs in the record

  • The proposed purchase and full cost
  • The authority required
  • The unresolved delivery question

What does scrolling approve?

Nothing. You are inspecting a proposed workflow; this page cannot authorise a purchase.

Record

Keep the reasoning through to settlement.

The buying brief, sources, open question and decision request form one readable thread. In a real trade, delivery and payment records would join it as those events occur.

The linked purchase record

EXAMPLE

Delivery obligation met + payment settled → fee assessment

What belongs in the record

  • The decision and its supporting sources
  • Evidence that the delivery obligation was met
  • The settled payment and its matching record

When can a fee be assessed?

Only when the delivery obligation has been met and payment has settled. This example has neither event and records no earned fee.

A useful record makes the next decision clearer.

This page explains the intended workflow. It is a designed example, with no customer transaction or performance result behind it. Product capabilities and access are still being developed.

Explore the workspaceUnderstand authority and control