Treviya
For · Logistics partners

Logistics as ameasurable surface.

Treviya works with 14 3PL partners across six regional hubs. Every hub inspection, every proof of delivery, every exception is a data point on an active scorecard. This page is the operating standard.

14
3PL partners
6
Regional hubs
0.3%
Platform damage rate
Why partner with Treviya

Treviya is a short-cycle, short-commitment wholesale commerce platform with predictable volume across clear categories and lanes. For 3PL partners, that translates into stable flow, without the per-cycle novelty that makes ad-hoc importer work expensive to service.

We are deliberate about how the relationship is structured. Categories are chosen before a partner is onboarded. Inspection workflows are written up and attached to the partner master terms. Volumes are forecast by lane and refreshed quarterly. Partner performance is visible to both sides on a shared scorecard.

Operating workflows
Hub inspection submission

Every arrival is re-inspected at the hub against the cycle sample plan. Inspection reports upload through the partner portal with structured fields (grade, moisture, defect count, foreign matter, packaging integrity) plus photos and inspector signature.

POD upload

Proof of delivery is uploaded within 48 hours of last-mile delivery. Target is documented as a platform-wide SLA. POD metadata (timestamp, signatory where applicable, carrier exception notes) writes to the ledger on upload.

Capacity forecasting

Quarterly capacity forecasts per hub per category, refreshed monthly. Variance against plan is a scorecard input. Underforecasting or overforecasting is itself a signal.

SLA monitoring

Arrival inspection turn-around, POD upload lag, exception-response lag and damage rate are tracked per cycle. Thresholds are written into the partner master terms.

Exceptions handling

Damage, quarantine, customs hold and delivery refusal each have a defined workflow with evidence upload and timed escalation. Exceptions never live in email, they live on the cycle record.

Partner scorecards

Four domains per quarter: timeliness, integrity, communication and exception handling. Scorecards are visible to the partner and drive lane assignment for the next quarter.

Communication standards

Platform-to-partner

Cycle-level briefs published in advance with volume forecasts, inspection plans and SLA targets. Monthly scorecard delivered to the partner with four-domain breakdown. Quarterly review covering lane mix, capacity allocation and any incidents.

Partner-to-platform

Arrival acknowledgement within 4 hours of dock-in. Inspection report within the cycle-level target. POD within 48 hours of last-mile. Exception reports on the same day a deviation is identified. All reports submitted through the partner portal, never by email alone.

Partner-to-member

Partners do not communicate directly with members. All member-facing communication flows through Treviya's member desk, with evidence drawn from the partner submissions. This protects member privacy and keeps the cycle record consolidated in one place.

Onboarding
Phase
01
Application

Partner application with lane, category, hub capacity and SLA commitments. Reviewed by operations + compliance.

Phase
02
Verification

Licence, insurance, bonded-warehouse status where applicable, references and a physical site visit.

Phase
03
Pilot

Two-cycle pilot on a low-complexity lane. Scorecard established from the first cycle.

Phase
04
Active

Regular lane allocation against the partner scorecard. Continuous monitoring.

Read next
Begin

Measurable.Accountable. Stable.

If your hub operates to this register, we'd like to talk. Apply through the partnerships contact path.