FAQ
Answers for operators evaluating or running Limen Fulfillment.
What is Limen Fulfillment?
A multi-tenant warehouse and order platform for fulfilment operators. Each operator gets an isolated workspace; merchants are stores inside that database.
Who is the tenant?
The fulfilment operator is the tenant. Merchants are not separate tenants — they are store records scoped inside your operator database.
Which channels and carriers are supported?
The integrations page lists marketplaces and carriers we connect today. Your operator workspace enables the accounts you configure.
How do staff sign in?
Floor and office users sign in on your operator subdomain URL, not on this marketing site.
Where is data hosted?
Production hosting and data residency follow your operator agreement. Each tenant database is isolated from other operators.
How do we request a demo or new environment?
Use the contact section on the home page or email the address in the footer. Sales and onboarding reply during Riyadh business hours.
Who controls merchant and customer personal data?
Your fulfilment company is typically the controller for data processed to store, pick, pack, and ship for merchants. Limen processes that data on your instructions. Merchants and end customers should receive privacy information from you, not from this marketing site alone.
Is each operator's data isolated from others?
Yes. Each operator tenant has its own database. Store and warehouse identifiers from one tenant cannot access another operator's workspace.
Do you use our order data to train public AI models?
No. Operational data in your workspace is used to run your fulfilment service, not to train general-purpose models sold to third parties. If optional AI features are enabled for your tenant, their scope is described in your agreement and product settings.
What cookies does the marketing site use?
Session and locale preferences, plus security tokens required by Laravel. We do not run ad trackers on limen.ai marketing pages. Operator sign-in uses separate session cookies on your subdomain.
How do we request deletion or export of workspace data?
Use your workspace administration tools where available, and contact your account team for contractual export or deletion at end of service. Timing follows your operator agreement and legal retention duties.
Where are integration credentials stored?
Store, carrier, and finance credentials are stored encrypted in your tenant environment and scoped to the accounts your staff configure. Rotate keys in the provider and in Limen if staff leave or integrations change.
Can merchants log into our operator workspace?
Merchants use the merchant portal or API scoped to their store — not the full staff dashboard. Your RBAC defines which operator staff see which stores and warehouses.
What happens when we stop using Limen?
Your contract defines the notice period, data export window, and deletion timeline. Plan carrier and channel disconnects so orders in flight complete or transfer cleanly.
Does Limen comply with Saudi privacy rules?
We design for tenant isolation, access control, and processing agreements suitable for Saudi fulfilment operators. Your DPA and privacy notices to merchants should reflect your role as controller and any cross-border hosting in your contract.
Questions about these policies? Email us at
hatem@isnaad.aiReady to see Limen in your warehouse?
Book a walkthrough with our team or explore the integrations your operators use today.