What can deviate,and how we hold the line.
Physical commerce is complex. Cycles can deviate from the model at several points in the lifecycle. Treviya documents the scenarios, the effect on a cycle and the discipline in place to address them, upfront, not in the small print.
Trust is not the absence of risk. Trust is the public documentation of what could occur, who handles it and what remains on the record. The sections below are the safeguards behind every Treviya cycle, written in the same plain register that appears on the brief, the ledger and the settlement statement.
Each scenario is listed with the issue, the effect on the cycle, the platform response and the operational discipline that keeps the response accountable over time.
A vetted supplier fails to deliver against the cycle contract, short shipment, missed window, refusal to honour spec.
The cycle may be paused, shortened or cancelled. Members may receive a partial allocation, a revised window or a full return of reserved credits depending on the stage at which non-performance is identified.
Gate 2 of the six-gate curation framework carries the primary weight, licence, UBO, sanctions, references, factory audit and sample testing. For active cycles, a supplier desk monitors shipment and milestone acknowledgements. A supplier scorecard tracks every cycle and feeds back into future eligibility.
Suppliers with a documented non-performance event are placed in review. Second material events lead to removal. The supplier directory publishes the current status of every active supplier.
Delivered goods fail to match the grade, specification or safety profile documented on the cycle brief, moisture, foreign matter, colour, chemistry or packaging.
Affected units are quarantined at the regional hub. The cycle pauses pending replacement, re-grade or partial credit. Settlement reflects the outcome line-by-line.
Origin inspection plus independent hub re-inspection. Chemistry reports where applicable (oil, honey, cosmetic raw materials). Independent lab testing for flagged lots. Batch-level quarantine workflows documented on the cycle record.
Every quality exception is logged on the cycle exception log. Revised settlement statements reference the original ledger entries, records are never overwritten.
A shipment misses its booked window, port congestion, carrier exception, customs hold or hub capacity constraint.
The cycle window shifts. Members are notified. If delay exceeds the contracted bound, the platform may exit the contract and refund the cycle in full.
Continuous visibility across 14 3PL partners and six regional hubs. Contingency routing on high-volume lanes. Pre-agreed substitute carriers for common categories. Customs counsel for destination jurisdictions.
SLA monitoring against every shipment. Quarterly carrier scorecards. Carriers below threshold are rotated out of active lanes.
For cycles authorised to resale, the partner channel mix clears below the modelled base case, slower uptake, price compression or inventory saturation in the destination market.
Realised net proceeds settle below the base case. The cycle outcome is marked below base case on the archive alongside cycles that settled within or above. Records are complete, the drivers are visible.
Gate 4 (competitive scan) is the primary safeguard upstream: live pricing, stock depth and saturation checked before the brief goes public. For active cycles, channel mix is adjustable during the window. Channels below threshold are rotated.
Every cycle outcome, above, within or below base, is published. Selective presentation of history would undermine the record-keeping standard the platform is built on.
Destination market pricing shifts during the cycle window, a larger incumbent drops price, a seasonal event concludes earlier than expected or category demand softens.
Realised channel prices may clear at a different level than the brief indicated. The margin model shows three scenarios (conservative, base, optimistic) so the range is pre-disclosed.
Gate 3 (margin modelling) anchors decisions on the conservative case. Cycles that fail to clear the conservative threshold at gate review are declined. Base-case disclosure is binding and auditable.
Margin scenarios on the brief are written before authorisation opens. If a cycle later settles at a level not previously modelled, it is documented and the modelling framework is reviewed.
Cross-border cycles expose cost or settlement figures to FX movement between authorisation and close.
Currency variance appears as a dedicated line on the settlement statement. It is neither absorbed silently nor hidden in another cost line.
Cycles are priced in local currency where feasible. For cross-border lanes, hedging policies apply per the disclosed treasury framework. Variance is shown as its own settlement line so the effect is isolated.
Hedging decisions sit with the platform treasury function under a documented policy. Any change to the policy is published before the next cycle it affects.
A jurisdiction introduces a new import duty, labelling requirement, sanitary control or sanctions update that affects an active or forthcoming cycle.
Cycles may be rescheduled, re-routed to a different hub or cancelled outright. Members are notified with the regulatory citation and the path forward.
Compliance desk monitors UN, OFAC, EU, UK and Swiss SECO lists continuously, plus origin-and-destination regulatory feeds. Category restrictions and sanctioned-origin exclusions are applied at gate one.
Sanctions and category restrictions are hard gates. Commercial incentives never override regulatory exclusions.
A platform outage or degraded state affects visibility, authorisation or settlement timing.
Affected operations pause until service is restored. No cycle commits during degradation. Post-incident, a written post-mortem is published on the public status page.
Multi-region monitoring with continuous health checks. RTO ≤ 4 hours for catastrophic failures; RPO ≤ 15 minutes on ledger and account data. Published incident history, retained 12 months.
Material incidents receive post-mortems within 72 hours. Post-mortems are blameless and include root cause, contributing factors and corrective actions.
Six-gate evidence. Supplier documentation. Sample-test results. Margin scenarios. Curation committee decision.
Milestone acknowledgements. Origin and hub inspection reports. Carrier exception notes. Channel partner dispatches.
Settlement statement. Ledger export. Exception log. Revised statements where applicable. Archive entry.
Each deviation scenario with its documented path and retained record.
FATF, sanctions, data protection across the jurisdictions we operate in.
Why every cycle generates evidence, how it is retained, how it is exported.
Written before the cycle.Retained after close.
The safeguards above are not hidden in terms of service. They sit on this page, on the briefs and on the cycle records, in the same words.