Garages & auto repair
An accessory, a set of wiper blades, a routine maintenance part get ordered on the phone. Availability read at the source saves tomorrow's callback.
Helping somebody choose the right items, then getting an order genuinely confirmed by your store — rather than an intention noted somewhere.
7 days, 20 answered calls, no card
Calls beginning with “do you have…?” too often end with “let me check and call you back.” In between, somebody hung up and ordered elsewhere. The problem is not selling: it is knowing, during the conversation, what is in stock and at what price.
This add-on reads the items of the store you connected: variants, availability and current price. The conversation helps a person choose, prepares a recalculated cart with its pickup or delivery terms, and has them confirm what they are taking.
The store keeps the record of the order: the order is confirmed when your store confirms it. That way, every sale announced to a customer is in your system.
Items, variants and availability are read in the connected store. An answer about stock comes from the source, rather than from a copy refreshed last week.
The cart is prepared under standard pickup or delivery rules. The calculation is the store's, and a person sees what they are taking before going further.
A person confirms, then payment happens inside the provider's own flow. The order is recorded once the store genuinely confirms, and not before.
Order status is tracked on the file. A cancellation or return request is created as a request: by itself it authorises no refund.
The add-on includes collecting payment for its own orders. For your ordinary invoices, use the Deposits and payments add-on.
It works with your accounting, your inventory and your commerce platform without replacing them, and with the store you already have. For a restaurant, the industry's connected ordering is enough: this add-on serves a separate retail store.
An accessory, a set of wiper blades, a routine maintenance part get ordered on the phone. Availability read at the source saves tomorrow's callback.
Counter-sold material is reserved during the call. Pickup is confirmed with its terms, and a customer file keeps a record of what was taken.
Products sold after a service are repeat sales. Ordering them inside the conversation beats a callback that will not happen.
Food or a care product gets reordered regularly. The order follows its statuses, and a return request stays a request subject to your decision.
A refund stays your decision, separate from collecting payment. Executing a cancellation depends on what your store provides for.
The add-on carries its own monthly volume, which you follow in your app: order journeys, one connected store and the payment requests for those orders.
Your contracts with your payment provider and your commerce platform stay yours, at their own rates.
The connected store keeps the record of the order, and the connection is authorised from your account.
The customer confirms the cart, then your store confirms the order: the store keeps the record. That way, every sale announced to a customer is in your system.
From the connected store, read at the source: items, variants, availability and current price. An answer about stock does not come from a copy refreshed last week.
Yes, as a journey, without becoming a sale. A journey starts once somebody explicitly engages a cart and counts once; a product question, a stock read or tracking an existing cart create no further journey.
No. The add-on works with your accounting, your inventory and your commerce platform, and with the store you already have.
No. A cancellation or return request is created as a request: by itself it authorises no refund, and executing it depends on what your store provides for.
Payment in other cases, or the conversation carrying an order.
Orders from your store