← Back to PickStack

How we judge the PickStack pilot

For businesses only. This pilot is not available to consumers.

The pilot covers 10 planned orders. One planned order means one customer order planned onto pallets.

€500 — no VAT charged (LuceneX is not VAT-registered).

If the plans don't meet the pilot success criteria, we refund the full €500. This page sets out those criteria in plain English.

PickStack is still being built. The pilot is how we test it on real (already shipped) orders.

1. What we compare

For each pilot order, we compare our plan with what you actually shipped.

This is a method, not a promised outcome. We don't promise savings, fewer pallets, a fill level or any other business result. What we do promise is a clear, per-order test that both sides can check.

Everything is recorded on a shared comparison sheet that both of us can see and comment on throughout the pilot. We fill in the plan columns when we deliver each plan. You fill in what you shipped. Facts come from the record:

• the plan as delivered, for plan data
• your inputs, for your rules
• your shipping records, for what you shipped (a WMS export, packing list or delivery note, with personal data removed)

Neither side's opinion decides the result.

2. When an order counts as failed

An evaluated order fails if any one of these is true:

1. The plan is late. No plan was delivered by the delivery deadline (see section 6).
2. The plan breaks one of your rules, or fails a physical check PickStack supports. On any line that isn't flagged for manual review and isn't non-palletisable, the plan breaks a rule you gave us in your inputs, or fails one of these checks against the limits you supplied:
   • every unit's footprint fits within your pallet
   • the pallet's estimated height stays within your maximum height
   • the pallet's weight stays within your maximum weight
   • the tier order (bottom, middle, top) respects your stacking rules: heavy or sturdy items at the bottom, fragile items at the top, and any maximum weight on top you gave us
   • PickStack's area-utilisation check holds (a heuristic for how much of the pallet area the units take up, not an exact layout)

   Your rules include maximum pallet weight, maximum load height, footprint or overhang limits, stacking, fragility or orientation rules, and mixing or segregation rules. Plans describe tiers (bottom, middle, top) of units, not exact positions, so we don't score exact carton positions or 2D overlap.

   If a pallet can't be built as tiered. Because a plan doesn't give exact positions, it can pass these checks and still turn out not to be buildable as tiered. If you document that a pallet can't be built as tiered, the order fails, but only when the cause is the plan itself, not one of your rules or data you didn't supply.

3. A palletisable line is left off. The plan leaves any palletisable order line off a pallet. Lines over your pallet footprint, weight or height limits are listed as non-palletisable and aren't treated as missing (see below). Any other line left off a pallet, for example because of the area-utilisation check or a maximum pallet count, counts as missing. Lines flagged for manual review appear on the manual-review list, not as left off.
4. The plan uses more automated pallets than you shipped. We compare the number of pallets PickStack planned automatically with your actual pallet count for that order, which is part of your inputs. Pallets suggested for manual-review items, and pallets added only because goods have unknown contents, aren't counted. The only exception: every extra pallet is needed only because your actual shipment broke one of your own rules (including the default rules you confirm at the start), and we show this on the comparison sheet with evidence from the record.
5. Too much cap-counting manual review. More than 20% of the order's other lines are cap-counting manual-review items, meaning anything flagged for manual review outside the two mandatory review categories below. "Other lines" means evaluated lines, not counting non-palletisable lines.

Mandatory review doesn't count toward the 20%. Two categories always go to manual review and don't count toward that 20%: items with a hazard flag, and fragile items where you didn't give a maximum stack weight. Hazardous goods are flagged for manual review. Every other manual-review item counts toward the 20%, including items PickStack rates as high-risk. We sort each flag into one group or the other from the reason PickStack gives, using the mapping on the comparison sheet. A line that's openly flagged for manual review is not a rule break.

Non-palletisable lines. Lines over your pallet footprint, weight or height limits are listed as non-palletisable. They are not "missing" and do not count toward the 20%. PickStack lists the lines it leaves off a pallet. We check each one against your pallet limits and list it as non-palletisable only if its footprint is larger than the pallet, its weight is over your maximum load, or its height is over the usable height. That classification is recorded on the comparison sheet. The order is judged on its other lines. If every line in an order is non-palletisable, the order is excluded as a reason on your side (see section 4).

3. When you get the full €500 back

You get the full €500 back if any one of these applies:

1. Too many orders fail. At least 40% of evaluated orders fail, rounded up.

   Evaluated orders	10	9	8	7	6	5	4	3	2	1
   Failed orders that trigger a refund	4	4	4	3	3	2	2	2	1	1

2. A plan never arrives. On the last day of the pilot window, any order you submitted with complete inputs in time still has no plan. "In time" means at least 5 Business Days before the window ends.
3. Too few orders can be evaluated, and it's our fault. Fewer than 5 orders can be evaluated, and at least one order was excluded for a reason on our side.

If fewer orders can be evaluated only for reasons on your side, the pilot is judged under points 1 and 2 on the orders that were evaluated. An order excluded because all of its lines were non-palletisable counts as a reason on your side.

The 20% and 40% figures are pass/fail criteria. They aren't performance claims.

4. What's excluded, and why

An order is evaluated only if both of these are true:

• you sent complete inputs within the pilot window, and
• either our plan was late, or you supplied what you actually shipped and that shipment covered the same lines, quantities and pallet type as your inputs. Differences we both record as immaterial are allowed.

Orders that don't meet this are excluded. They are not failures. The comparison sheet records the reason, and whether it was on your side or ours:

• Your side: inputs weren't complete, no record of what was shipped, the shipment differed from the inputs, or every line in the order was non-palletisable.
• Our side: we didn't send the intake spec on time, we rejected inputs that matched the spec, or we couldn't accept or process inputs for a reason within our control.

Order lines you didn't ship on pallets (for example, shipped loose or separately) are left out of that order's evaluation.

A late plan still counts. If our plan is late, the order is evaluated and fails, even if you haven't supplied what you shipped.

Why exclusions exist: a fair comparison needs both sides, meaning complete inputs and a matching record of what was shipped. We plan on the inputs as you supply them. A plan isn't counted as failed because inputs were wrong, incomplete or inconsistent, or because it breaks a rule you didn't give us.

5. Informational only: fill rate

We show fill on the comparison sheet: our plan's fill, and yours if you have it. It is information only, not a pass or fail test.

Why: with the same items and pallet type, fill moves with pallet count, and pallet count is already tested in section 2. Also, few businesses measure the actual fill of shipped pallets.

6. Timing

• Start: you accept the written pilot terms, we invoice, and you pay. The pilot starts when we receive the €500. Within 2 Business Days after that, we send you the intake spec and the comparison sheet.
• Pilot window: 60 days from when we receive the fee.
• One-time extension of the pilot window: if you ask in writing before the window ends, we extend it once, by up to 30 days. This is separate from the refund-request period below.
• Completeness check: within 2 Business Days of receiving your inputs, we confirm they're complete, or list exactly which mandatory fields are missing. If we don't reply in that time, your inputs count as complete.
• Delivery deadline: each plan is due within 5 Business Days after your inputs are confirmed complete. A plan delivered after that is late.
• Unused orders: orders not submitted with complete inputs within the pilot window lapse. That alone doesn't give you a refund.
• Pilot End Date: the last day of the pilot window, or earlier if the last plan has been delivered and all comparison-sheet rows are complete.
• Refund-request period: send a written refund request (email is enough) to info@lucenex.eu within 30 days after the Pilot End Date, pointing to the comparison sheet.
• Our response: within 5 Business Days, we may point out a factual error in the comparison sheet, with evidence from the record. We can't refuse a refund on any other ground if the record shows a refund trigger. If we don't respond within 5 Business Days, your request is accepted.
• Refund payment: we pay the full €500 within 14 Business Days after your request is accepted (or deemed accepted if we do not reply within 5 Business Days), to the account you paid from or another account you name in writing, without deductions, unless mandatory law requires a shorter period. If we raised a factual point, the 14 Business Days run from when that point is resolved and your request is accepted.

Business Days are Monday to Friday, excluding Latvian public holidays.

7. What you provide

The pilot uses already-shipped orders only. That way, what you shipped is known from the start and the pilot doesn't touch your live warehouse operations.

For each order:

• an order ID (an internal reference, not a customer name)
• order lines, SKUs and quantities
• unit or case dimensions and weights
• packaging and stacking rules, including any lines your rules say a person must handle
• pallet type and limits: footprint, maximum height and maximum gross weight
• any mixing or segregation rules
• what you actually shipped: your actual pallet count for the order (required), pallet type, and any fill, weight or height data you hold

At the start, you confirm or change PickStack's default rules on which goods can't share a pallet and whether temperature zones may be mixed. Once confirmed, they count as your rules. Goods with unknown contents are always kept on their own pallet; that can't be switched off.

We'll confirm how files are shared after upload terms are set. Interest: booking link or info@lucenex.eu.

PickStack is EU-hosted. How uploaded files and plans are stored, retained and deleted: data handling terms

Historical order exports often contain consignee names or delivery addresses. Please remove these, and any other personal data such as phone numbers or driver details, before you share any file. If we receive personal data by mistake, we delete it and tell you.

You don't need to tell us a pick direction or pick sequence. It isn't an input, and it isn't part of the pass/fail test.

8. What you get for each order

Each plan comes as a JSON plan file plus a derived PDF summary. The JSON file is PickStack's own export. The PDF summary is prepared by LuceneX from it and shows, for each pallet, the SKUs and quantities in each tier (bottom, middle, top) and the pallet's estimated height. The plan also lists items flagged for manual review and any lines left off a pallet. It describes tiers of units, not exact positions within a tier.

You can keep using the plans we deliver for your own internal business, including after a refund. The PickStack software, models and algorithms stay with LuceneX.

9. Small print

• Plans are recommendations. PickStack plans are planning recommendations. You check them before use, and you remain responsible for physical execution: building and securing loads, vehicle and axle weight limits, load-securing and transport rules, dangerous goods, and workplace safety.
• Dangerous goods. Hazardous goods are flagged for manual review. PickStack doesn't plan dangerous-goods segregation unless we agree that in writing.
• Tiers, not exact positions. Plans give tiers of units for each pallet, not exact positions, so you check that each pallet can be built before you use the plan.
• Evaluation, not production. The pilot is an evaluation of pre-release software, provided as is. We don't promise savings, pallet reduction, a fill level or any other business result, or that plans will be error-free.
• Businesses only. This pilot is not available to consumers.

10. Company

SIA "LuceneX"
Registration no. 40203713932
Siguldas iela 2-68, Vangaži, Ropažu nov., LV-2136, Latvia
info@lucenex.eu