Request a Quote
A correct order should be boring. A quote becomes unreliable when key inputs are missing. Then the number is a guess, and guesses turn into exceptions later.
- Defined inputs
- Controlled checks
- Clear handoffs


GET A QUOTE
GET A QUOTE
We don't run a price calculator. We use your inputs to prepare a clear scope call that defines what we execute, what we don't, and what stable operations should cost.
On the scope call, we confirm dependencies, define what's in/out, and agree on what "done" looks like operationally: inventory truth, closure with proof, and controlled exceptions.
If the project is a fit, you'll get a scoped proposal. If something critical is missing, we'll ask for clarification before we accelerate. A proposal without clear inputs is a guess. We don't guess on projects.
If you're not ready for a scoped request—you just want to chat about fit or confirm constraints—use /contact/ instead. That page is for fast routing and quick questions. This page is for projects where scope is the priority.


MINIMUM INPUTS
MINIMUM INPUTS
You don't need a perfect dataset. You do need enough to avoid operating blind. Share what you know. We'll ask for clarification where it matters.
What to send us (so the conversation isn't blind)
You don't need a perfect dataset. You do need enough to avoid operating blind. Share what you know. We'll ask for clarification where it matters.
1) Your operation at a glance
- Channels in play (eCommerce, Amazon, B2B/retail, or mixed)
- Where you sell (Spain only, EU, UK, or a mix)
- Expected go-live window and any hard dates (launch, promotion, seasonal peak, retailer deadline)
- Current volumes: rough order count per month and SKU count in active rotation
2) Orders and volume shape
- Typical daily orders and peak pattern (do volumes spike for promos or seasonality?)
- Average lines per order and percentage of multi-item orders
- Cut-off logic (same-day dispatch vs. next-day vs. flexible)
- Typical destination mix (Spain / EU / UK, and roughly what percentage each)
3) Product and SKU structure
- Number of SKUs in active rotation and rough variant count (sizes, colors, configurations)
- Unit dimensions and weight range (rough is fine; we refine later)
- Fragility, handling constraints, or special compliance needs (if any)
- Any products with lot/expiry tracking requirements
4) Inbound and how stock arrives
- How goods arrive: cartons, pallets, containers via forwarder, or mixed
- Frequency of inbound (weekly, biweekly, monthly) and typical batch size
- Any receiving verification needs (counts, condition checks, sampling/AQL if applicable)
- Whether lot/expiry tracking is required; we evaluate case-by-case
5) Special work (only if it applies)
- Kitting or pack builds (assembling multi-component sets)
- Labeling or relabeling requirements (custom labels, reprints, barcode replacements)
- Amazon prep needs or special requirements for specific marketplaces
6) Returns and reverse flow
- Rough returns rate and the reason profile (damage, size wrong, defect, buyer remorse, other)
- Required triage outcomes (restock / refurb / rework / quarantine / scrap)
- Any special handling for returns (inspection before restock, time window, etc.)
7) Systems and data handoff
- Store/marketplace in use (Shopify, WooCommerce, custom, etc.)
- ERP/OMS if you have one (Odoo, SAP, Netsuite, custom, or just order exports)
- How orders and inventory sync today (API, CSV export, manual, or where it breaks)
- Any special data needs (bundle definitions, custom fields, B2B references, etc.) Helpful (optional): If you have them ready, a SKU list with dimensions/weights, a sample order export (20-50 lines), or a returns summary (reasons + outcomes) speeds up scoping. A photo of current packaging is helpful only if protection or presentation is a known issue.
WHAT YOU GET BACK
WHAT YOU GET BACK
A quote is not just a number. If we move forward, you'll receive:
We don't estimate based on rough guesses. We scope based on your inputs and our experience with similar flows.
- A clear scope: what we execute (receiving, inventory, picking, packing, dispatch, returns) and what we don't (cold chain, ADR 1/7, storage-only, inventory financing)
- The control points that keep the flow stable: what inputs we need, what checks happen at each step, what closure looks like
- A proposed operating model: the modules (receiving, inventory, picking, dispatch, returns), handoffs between them, and how communication flows
- A commercial proposal aligned to that scope, with pricing tied to volume, channels, and special work


TYPICAL TIMELINE
TYPICAL TIMELINE
This timeline assumes your inputs are clear. If we need more information (more detail on SKU variants, current exception patterns, or channel-specific rules), we ask. The timeline pauses until we have what we need.
- Submission to initial response: We reply within 2-3 business days with questions if any inputs are unclear
- Scoping call: Typically scheduled within 1 week of your response
- Call duration: Usually 45 minutes to 1 hour, depending on flow complexity
- Proposal delivery: Within 5-7 business days after the call, if we move forward


WHAT DOESN'T WORK
WHAT DOESN'T WORK
We can't scope reliably if:
We'll ask for clarity on all of these anyway. But if you're not ready to answer, the scoping call will take longer or we may ask you to gather this information first.
- No defined flow: You haven't decided what "done" looks like (speed vs. proof vs. returns discipline). We'll ask you to define it.
- No SKU data: You can't tell us how many SKUs you have or what they are. We'll need at least a top 20 SKU list to start.
- No channel clarity: You don't know your order sources or volumes. We'll ask for clarification.
- Missing inbound expectations: You don't know how goods arrive or in what condition. We'll ask for this before we commit.


LIMITS
LIMITS
We don't promise what we don't control.
If your product has special compliance needs (lot tracking, fragile handling, unusual packaging), we evaluate case-by-case and confirm scope before committing.
- No cold chain / temperature-controlled storage. We do not operate refrigerated or climate-controlled space.
- No ADR classes 1 and 7. We do not handle explosives or radioactive materials. For other hazmat categories, we evaluate case-by-case.
- No storage-only warehousing. We work with defined flows and live inventory. Inventory must be moving and reconciling, not sitting without operational context.
- We do not finance or own client inventory. You own the goods and the commercial decisions. We execute the flow.


NEXT STEP
NEXT STEP
Fill out the form below or send us an email with the inputs above. If you can, include one example: one SKU, one typical order, and one recurring issue you want to stop repeating. That's enough to start a scope call that isn't guesswork.
Map your flowFAQ