FAQ
The questions buyers actually ask
Switching the system that runs your warehouse and your Amazon business is a serious decision. Here are straight answers to the objections that come up most.
- Who owns our data, and can we get it out?
- You own every record your tenant produces. Catalog, inventory movements, orders, shipments, and audit history are yours, and you can export them to CSV from the app at any time. On request we provide a full structured export, including the append-only ledger, in machine-readable form. There is no lock-in clause that holds your operational data hostage.
- What is the downtime and cutover risk when we switch?
- There is no big-bang weekend. You run FulfillPath in parallel with your current stack for an agreed window while both systems process the same activity. Cutover is not a date on a calendar; it is the moment the reconciliation report shows every SKU matching. Until then your existing systems keep running, so a problem on our side never stops you from shipping.
- What happens if reconciliation never fully clears?
- You do not cut over until it does, so a stuck reconciliation is a reason to stay in parallel, not a forced go-live. Every discrepancy drills down to the exact ledger movements behind it, which usually surfaces a data error in the source system rather than a FulfillPath problem. We work the exceptions with you, one SKU at a time, and the pilot tenant keeps running against your current stack the whole time at no risk to production.
- What support and SLA do we get?
- Every plan includes email and shared-channel support during business hours with a same-business-day first response target. Growth and Pro add priority response and a named contact for onboarding and escalations. Uptime, response-time, and escalation commitments are written into the order form so they are contractual, not marketing. Enterprise agreements can add extended-hours coverage.
- How is our data secured?
- Tenant isolation is enforced in the data layer: every business table carries an org identifier and the query layer injects and enforces it, so a request with no tenant in scope is rejected rather than returning cross-tenant rows. Channel and carrier secrets are encrypted at rest with AES-256-GCM in per-org credential rows. Access is granular role-based permissions, high-risk actions require a second approver, and every mutating action writes to an append-only audit log. Users can enroll TOTP MFA, and an admin can require it org-wide. See the security page for detail, and bring your questionnaire.
- What do the contract and onboarding look like?
- Pricing is per tenant on a monthly or annual term, billed per tenant and scaling with order volume, with no per-seat surprises on the ops core. Onboarding starts with a scoped migration: we import your catalog, bins, opening inventory, and open POs, run a dry-run validation report, then move into the parallel run. You are not committed to production until reconciliation is clean, and annual terms include the migration and parallel-run window rather than charging for it separately.
- Do we have to move everything at once?
- No. The platform is phased by design. You can start with the ops core (catalog, inventory ledger, WMS, purchasing, Amazon FBM, and shipping) and add the margin modules such as FBA prep, profitability, repricing, and reimbursements later by turning on the relevant plan or feature flag. Each add-on is gated per org, so you enable what you need when you need it.
- What happens to our existing bin labels and hardware?
- Your existing bin label codes come across unchanged, so nothing needs reprinting on day one. The scanner app runs in any modern browser on rugged Android devices and works with Bluetooth wedge scanners paired to a phone or tablet, so in most cases you keep the hardware you already own.
Still have a question?
Book a call and we will walk through migration, security, and pricing against your own numbers, or jump straight into the live demo.