1. Core-profile check
Does the complete packed order sit inside Vareya’s compact category working profile? The profile is under review and its boundaries are not published as a service limit.
Working method · version 0.1 · October 2026
The Vareya Boxable Product Framework
The framework is the working method behind Vareya’s Boxable assessment. It sets out how a complete packed order, its handling needs and its routes are reviewed together, and how the evidence behind each conclusion is labelled.
It is a working method, not a certified standard. It is not an industry standard, a carrier rule or a product approval.
Status of this method
Version 0.1 is a working method under review. It has not been calibrated on a published dataset and it is not a certified standard, an accreditation or an industry norm. We do not publish scores, score thresholds, weightings, rating scales or example products while that work is incomplete.
Nothing on this page should be read as carrier acceptance, product approval, a quotation or a promise of a particular result.
What the framework is for
The framework gives Vareya one consistent way to review a product and order combination before describing a fulfilment setup. It is not a product database, and it does not classify a product forever.
The unit of assessment is not a product name in isolation. It is the SKU, the order combination, the complete packaging, the storage and handling process, the destination, the carrier service, the rate version and the date. An identical SKU can produce a different outcome in a different bundle or on a different route.
Working definition: a boxable product
In Vareya’s framework, a boxable product is an ecommerce item whose packed order can be stored, picked, packed and shipped efficiently using compact packaging. Physical fit, product safety, handling needs and carrier acceptance are checked separately. The core profile is a Vareya assessment rule, not a universal carrier limit.
Measurements use the complete, closed parcel: outside dimensions including bulge, protection and label requirements, and the total packed weight. Irregular shapes are recorded using the measuring rule of the relevant service. A bare product dimension is not a packed-parcel measurement.
Three layers
2. Acceptance gates
May and can the order be stored and carried under the agreed conditions? Six gates are checked in order, each with its own pass, review or stop outcome.
3. Efficiency and evidence
How straightforward is the accepted setup, and how well is that supported? Ten factors carry a rating and an evidence status.
A favourable efficiency view never overrides a failed gate. A missing fact is unknown, not automatically good or bad. A known safety, packaging, carrier or commercial stop comes before the core classification, not after it.
The ten factors
The draft model looks at ten factors. They are listed here so the method can be understood and questioned. The weighting and rating scales are internal design choices and are not published as a standard.
| Factor | What it asks | Why it matters |
|---|---|---|
| Packed dimensions | What space does the closed, ready-to-ship order occupy, including protection and bulge? | Volume and shape affect storage, packaging and carrier fit. |
| Packed weight | What does the complete parcel weigh, including packaging, filler and label? | Weight affects handling and, together with dimensions, the chargeable weight a service applies. |
| Packaging efficiency | How much of the internal packaging volume is product rather than empty space? | Empty space can add cube and material without protecting the product. |
| Storage efficiency | How many saleable units fit a usable storage volume, including agreed separation? | Storage density changes the space a product range needs. |
| Shipping and total order cost | What does the order cost to fulfil and ship, set against its net order value? | A label rate alone is not the full cost of an order. |
| Pick and pack | How much active work does a typical order take, from task acceptance to ready-to-ship? | Handling time is part of the operational cost. |
| Damage risk | How likely is damage in transit, and what would replacement and claims handling cost? | Replacement, claims and lost repeat custom sit beyond the label price. |
| Returns complexity | How much work does a return create, including receipt, inspection and disposition? | A low-value item can cost more to process than to replace. |
| Carrier compatibility | Is there an accepted service for each main destination, and a second accepted option? | One route is not a network, and backup coverage matters at peak. |
| Scalability | Can the setup absorb the agreed peak for the same mix and shift pattern? | Average capacity is not peak capacity. |
The set is an expert design hypothesis. It is not a regression model, and the factors are not claimed to be independent of one another: dimensions influence storage and cost, while protection influences both damage risk and handling time.
The gates, in decision order
Gates are not weighted. Each one has to be satisfied for the setup under review. The sequence matters because a later commercial discussion cannot repair an earlier safety, product or carrier problem.
G0
Data completeness
Check: Packed weight and dimensions, order mix, destination and the rate or service version are known and traceable.
If not satisfied: Incomplete data means no definitive outcome. The missing facts are requested first.
G1
Core-profile check
Check: The complete packed order is compared with Vareya's compact category working profile.
If not satisfied: Outside the core is not a refusal. Wider Vareya fit is assessed separately. The profile boundaries are under review and are not published as a service limit.
G2
Product and storage
Check: Safety, legal status, documents, temperature, batch or expiry needs and other special requirements are identified.
If not satisfied: Unknown means review. A confirmed stop applies to that setup, not automatically to every Vareya service.
G3
Packaging and protection
Check: Protection, closure, leak, break or puncture risk and label space are checked against the agreed protocol.
If not satisfied: No test means review. A failed pack is redesigned before it is approved.
G4
Carrier and destination
Check: Written acceptance exists for the exact product, service and lane under consideration.
If not satisfied: No acceptance means that route is not used. A favourable efficiency view cannot compensate.
G5
Commercial and capacity
Check: Cost, contribution, labour and storage capacity and the contract scope are feasible for the operation.
If not satisfied: Unknown means review. A shortfall means a different setup or proposal, not a lower standard.
A known safety, packaging, carrier or commercial stop comes before the core classification. Then comes outside-core. Then incomplete data or review. A high efficiency result does not clear a gate.
Evidence status: how uncertainty is shown
Each factor carries an evidence status, alongside its source, period, sample and reviewer. The label is part of the result, not a footnote.
| Status | What it means |
|---|---|
| Measured (M) | Taken from a calibrated measurement or a recorded operational observation, with method, sample and date. |
| Documented (D) | Confirmed in a current document, such as a carrier service specification or a signed procedure. |
| Reported (R) | Supplied by the brand or an operational owner. Useful, but not independently measured by Vareya. |
| Assumption (A) | A stated design assumption used to explore a scenario. It is not evidence of how the order behaves. |
| Unknown (U) | No adequate source. Unknown is not zero, and it is not a pass. The factor stays open. |
Unknown is not zero. It is a gap that has to be closed or disclosed. A confidence view shows how much of the weighting rests on measured or documented evidence. It is a coverage measure, not a probability of success and not a statistical guarantee.
If a material factor is unknown, we do not publish a precise final result. A clearly labelled range may be used for internal discussion, but it is not presented as a product classification.
A result with thin evidence remains provisional. We require a reviewed evidence level before a result informs a commercial proposal; the internal threshold is not published.
What the framework does not do
- It is not a quotation, a price or a commitment to a rate.
- It is not carrier acceptance for a product, service or destination.
- It is not a product safety, legal or customs approval.
- It is not a certification, an accreditation or an industry standard.
- It does not replace measuring the packed parcel or testing the pack-out.
- It does not publish a score, score thresholds, weights or example products while the method is uncalibrated.
- It does not create a universal weight or size limit for Vareya’s services.
- It does not replace specialist advice on dangerous goods, customs or product compliance.
The measured packed parcel remains the operational fact. The framework is a decision aid, not a substitute for the tape measure or the carrier’s own conditions.
How the method is being validated
Validation is planned, not complete. Passing internal checks on the calculation and decision logic does not prove that the method predicts real operational outcomes.
The intended validation work covers:
- A pilot using real order profiles across straightforward, fragile, regulated and borderline cases, without selecting only successful examples.
- Two assessors reviewing the same profiles independently, with differences recorded per factor.
- Comparison with actual pick time, damage, returns work, exceptions and total order cost.
- Sensitivity checks on the weighting, so a small design change does not silently move outcomes.
- Version control, so earlier assessments keep the model version they were made under.
Until that work is complete, the framework is a working method for internal and client discussions. It is not evidence of performance, savings or predictive accuracy.
Version and change control
This is version 0.1, dated October 2026. The method page keeps a stable URL. Material changes to gates, factors or decision rules are recorded with a version and a date, and older assessments keep the version they were made under.
A public version 1.0 would require calibration, review and explicit approval. No date is promised, and no certification is implied by a version number.
What to prepare for an assessment
The more of these facts are available, the less the review has to rely on assumptions.
- Products and quantities in a typical order, including bundles.
- Closed, ready-to-ship dimensions, including protection and bulge.
- Packed weight, including packaging, filler and label.
- Packaging type and materials used for the current pack.
- Units per order and how variant mixes change the packed parcel.
- Storage conditions, batch, expiry or temperature requirements.
- Monthly order volume and the main destination mix.
- Current cost components: inbound, storage, pick and pack, packaging, transport and surcharges.
- The agreed returns process, including inspection and disposition.
- Product documentation or restrictions that affect storage or transport.
Frequently asked questions
What readers ask about the Boxable Product Framework and its limits.
Is the Boxable Product Framework an industry standard?
No. It is Vareya's working method, version 0.1. It is not a certified standard, not an industry standard and not a carrier rule. It has not been calibrated on a published dataset.
Can I see my Boxable score?
Not yet. The scoring model is under review and has not been calibrated. We do not publish scores, score thresholds, weights or example results while that work is incomplete. A conversation can still explain the factors, the gates and the evidence gaps for your order profile.
Does the framework set a universal weight or size limit?
No. It uses a compact category profile for assessment, but that profile is an internal design choice under review, not a service limit or a carrier rule. Vareya's published parcel profile is separate: combined dimensions below 900 mm with a maximum length of 600 mm, with product fit confirmed during qualification.
What happens when data is missing?
The factor stays unknown and the outcome stays provisional. We do not treat missing data as a zero or as a pass, and we do not publish a precise final result while a material factor is unsupported.
Does a good assessment mean my product is accepted?
No. Acceptance depends on the gates, the carrier service and the agreed scope. The framework organises the review; it does not replace carrier acceptance, product approval or a quotation.
Why ten factors?
They cover the physical parcel, the operation, the route and the commercial result. The set is an expert design hypothesis, not a regression model, and it does not claim to measure ten independent effects.
Is the framework used for every Vareya customer?
It is being developed as a consistent review method. It does not replace a quotation, onboarding tests or the agreed service scope, and it is not presented as a certification of any product or operation.
Start with your own packed order
Vareya will review your answers and send an initial fit response by email within one working day.