Programme revendeurs

Reseller pricing starts at 25 merchant stores. Below that you probably don't need it — the Business plan runs 5 stores for $50 a month with extra stores at $8 each, which is the cheaper way to serve your first handful while you build a pipeline. Planning a smaller launch and serious about the market? Tell us the plan and we'll look at it with you.

Reseller rates start at $6 per merchant store and $2 per staff seat a month, against list rates of $8 and $4. It is a monthly subscription, so that is what the account costs every month the stores are open — not a one-off joining fee. Staff seats are added in packs of 25, and the rate moves in your favour as you grow: around 100 stores we quote against your volume instead of the starting rates. Your final rate and terms are written into a proposal before you commit.

Whatever your market carries — we don't set it or cap it. Take App invoices you for stores and seats; your price list, your packaging, and your contracts with merchants are yours. Most partners wrap setup, training, and local support around the platform and sell the whole thing as one monthly service.

Territory is something we work through in the proposal. Tell us the market you want, the volume you're planning for, and what you'd commit to, and we'll take it from there.

Most of what a merchant and their customers see, but not all of it. Each store runs on its own custom domain with Take App branding switched off on the storefront, and on your own domain the dashboard shows your domain name instead of the Take App logo. Order email can go out from your own sending domain too. What stays ours: login and billing email, the Take App POS app, and the WhatsApp number messages are sent from until a store connects its own.

Take App's official WhatsApp number, until the store connects its own WhatsApp Business number. After that, order updates, delivery notices, broadcasts, and abandoned-cart reminders all go out from the merchant's number and replies land in that store's inbox — so connect it during onboarding, before a customer sees a name they don't recognize. Two things that catch partners out: messaging the number you just connected doesn't behave like a real customer's phone, so test from a separate handset; and built-in staff notifications follow store access, so give each merchant's team their own store and keep your own phone out of every order.

Per account. The included 1,000 automated WhatsApp messages and 2,500 emails a month belong to the subscription, and every store you run draws from the same pool. Anything a workflow sends counts — order updates, delivery notifications, reminders — while the messages customers send you, and the buttons inside a message already delivered, don't. Past the quota you can switch on pay-as-you-go at $0.05 per extra WhatsApp message. Usage is reported for the account as a whole rather than merchant by merchant, so if you plan to bill merchants for messages, expect to track that yourself.

Yes. The Platform API at platform.take.app covers products, customers, orders, inventory, and messages, with webhooks for order events and a Zapier app on top; API tokens come with the Business plan and above. A local cashier system nobody has connected before is a build rather than a setting — bring it to us early and we'll tell you honestly which one it is.

Yes — that is the other half of Enterprise. We design the site, add a mobile app where one is needed, and build the parts of a workflow that aren't settings. Local marketplaces, delivery networks, rental platforms, and booking sites have all been built this way; the branding on anything we build for you is agreed in the scope.

Each store can add as many drivers as it needs and assign an order to one of them by hand; the driver's number then goes on the receipt so the customer can reach them on WhatsApp. Delivery fees can be flat, by distance, by postal code, by zone, or by weight, and connected couriers quote live rates at checkout. What Take App does not do is dispatch by itself — it won't pick the nearest driver, batch orders into one run, or optimize a route. If a merchant's business depends on that, raise it early: it's a build, not a setting.

Customers browse and check out on the store page, and the order lands in WhatsApp for both sides — the checkout itself doesn't happen inside the chat. A store can skip the checkout page to get the WhatsApp message sooner, but then it collects the address and the details in the conversation by hand. WhatsApp's own rules sit on top: a business can reply freely only within 24 hours of the customer's last message, and Meta rate-limits automated template messages. Payments stay the merchant's own — each store connects its own gateway or takes bank transfer, a wallet, or cash, and Take App takes no commission on any order.

No — you invoice them yourself. Take App bills your Enterprise account for stores and seats, and there is no usage-based billing of your merchants inside the product, so charging a restaurant by its order volume happens in your own billing. If a client falls behind, you can switch that store's checkout off in its settings until they're current, without touching anyone else.

A dedicated account manager from the first call, a shared WhatsApp group with your team, and guided setup and training before go-live — for your whole operating team, not one person. Most of the platform is configuration rather than code, so your first merchant stores are usually live and taking orders in the same week.

Take App runs in 180+ countries with 100+ payment methods, and the storefront shows in 10+ languages — in the visitor's own browser language by default, or fixed to the one you choose for each store. Products are written by the merchant in their own words, so a catalogue reads in whatever language they type.