--- title: "How to take orders over WhatsApp | SilverCheckout" description: "Taking orders over WhatsApp, step by step: the cart is built in the chat, the payment link lands in the same thread, the paid order reaches your system." url: https://silvercheckout.co/en/how-it-works language: en-US site: SilverCheckout updated: 2026-09-27 --- # From first message to order, one record. In SilverCheckout, an order moves from first message to confirmation on one record. The customer sees every step in the conversation; your team sees the same record on the panel. 1. Draft 2. Cart 3. Link 4. Paid 5. Recorded 6. Being prepared Example: The states of order #1042. The last one is your order system's own status, read back into the conversation. ## One example sale, step by step. Built on SilverReply. The SilverOps team keeps the books. ### The product is found inside the chat. Customers describe what they want in their own words. Matching products come from your catalogue and the stock figure from your own system, and nobody is sent to another page. ### Questions get the business's own answers. Delivery, invoicing, returns: the answers come from the knowledge base SilverReply uses, which holds the business's own information, so nothing is written twice. ### The cart is built from what the customer types. The customer types "four tins". Product, quantity and total go straight onto the receipt, and nobody copies the order into a notebook later. ### The payment link arrives in the thread. A link carrying the cart's total lands in the same conversation. One step replaces the IBAN messages and the wait for a transfer slip. ### An unfinished order isn't forgotten. An order that stops at payment is followed up. The reminder goes out in the same conversation, with the same cart, so the customer never starts over. ### Confirmation and the record flow from one place. Once payment lands, confirmation follows, the order is written to your order system and stock updates. The order number and its status stay in that same conversation. ## Double entry. Every state is written twice: once in the conversation the customer sees, once on the panel your team sees. Both tell the story of the same order. Example order #1042, from both sides. | What the customer sees | State | What your team sees | | --- | --- | --- | | An answer to the question and two product options | Draft | The conversation opened, the catalogue searched, the stock checked | | A summary of the cart: product, quantity, total | Cart | The cart lines and total, taken from the conversation | | A payment link carrying the cart's total | Link | Order #1042, awaiting payment | | A message saying the payment arrived | Paid | Payment confirmation and its time | | The order number | Recorded | The entry written to your order system, stock updated | | The order's status, in the same conversation | Being prepared | The status coming back from your order system | ## Mid-sale, a person. Some sales are for your team to close. Here the customer asks for a price at volume, and SilverReply hands the conversation over to your sales team. They see the whole conversation and order #1042; the customer gets the answer in the same conversation. ## Each line, a different author. One record. Here is the example order on your team's panel. Example: the activity record of order #1042. | Time | Who | What happened | | --- | --- | --- | | Yesterday 10:31 | SilverGrow | A new-season follow-up went to a restaurant that ordered last season. | | Yesterday 10:42 | Customer | "Is the new harvest in?" | | Yesterday 10:42 | SilverReply | New-harvest question answered; two products suggested from the catalogue. | | Yesterday 10:44 | SilverReply | Delivery question answered from the knowledge base. | | Yesterday 10:46 | SilverCheckout | Cart created: 4 × early harvest 5 L. | | Yesterday 10:47 | SilverCheckout | Payment link sent: TRY 7,400.00. | | Today 09:30 | SilverCheckout | Unfinished order followed up. | | Today 09:41 | SilverCheckout | Payment received, written to your order system, stock updated. | | Today 14:05 | SilverCall | The customer rang to ask how invoices are issued; answered from the same knowledge base, call summary added to the panel. | | Today 16:28 | Sales team | The 40-tin enquiry taken over, with the whole conversation. | [SilverReply](https://silverreply.co/en), [SilverCall](https://silvercall.co/en) and [SilverGrow](https://silvergrow.co/en) share this panel and this knowledge base, and the same SilverOps team installs all four. ## Layers. SilverReply carries the conversation. SilverCheckout keeps the order. The same team installs both. - Order and payment: **SilverCheckout**. Builds the cart inside the conversation, sends the payment link into the same conversation, follows up unfinished orders and records every order. - Conversation: **SilverReply**. The AI sales and front-desk system from SilverOps. It greets customers on WhatsApp and website chat, answers from the knowledge base and hands the conversation to your team when needed. - Your systems: **stock and orders**. Supply product and stock details, take the order and send its status back. ## No receipt goes out behind the stockroom's back. An order taken in the chat is written to the business's own stock and order systems. Product and stock details come from there, the order goes there, and its status comes back from there into the conversation. 1. Product and stock details come into the conversation. 2. The cart is built; once payment lands, the order is written to your order system. 3. Stock goes down in your stock system. 4. The order status returns to the conversation. ## Read, written, returned. SilverCheckout reads from the business's own systems, writes to them and carries the status they return into the conversation. ### Read - products - prices - stock ### Written - the order record - payment confirmation ### Returned - order status Which systems it connects to is decided on the discovery call, and the SilverOps team builds the connections. If those systems are missing or scattered, the same team builds the ERP and stock side too. ## Installation. The SilverOps team keeps the books from the first line. - **Discovery call:** the SilverOps team and yours. Covers how your orders travel today, the channels, the stock and order systems and the payment step. Price comes after this call. - **Installation and integration:** the SilverOps team. The knowledge base and catalogue are prepared, the cart and payment step are set up, and your stock and order systems are connected. - **Operation:** the SilverOps team. Installation doesn't close the books; the same team runs the system. ## Three of the questions. ### How do you take orders over WhatsApp? The order is taken inside the conversation: the customer writes what they want, the cart is built in the chat and the payment link arrives in the same thread. [The full answer](https://silvercheckout.co/en/faq#whatsapp-orders) ### How does an order from WhatsApp reach a stock or ERP system? Once payment lands, the order is written to your order system and stock updates; the same order appears on the panel too. [The full answer](https://silvercheckout.co/en/faq#stock-erp) ### How is selling inside the chat different from an online store? In an online store the customer comes to the shop and finishes the payment alone; selling inside the chat closes the sale in the conversation the customer is already having. [The full answer](https://silvercheckout.co/en/faq#online-store) [All the questions](https://silvercheckout.co/en/faq) ## The record opens with a conversation. Our team first maps out with you how your orders travel today; which systems it connects to follows from there. [Book a call](https://silvercheckout.co/en/contact) [or message us on WhatsApp](https://wa.me/905425525162) · [+90 542 552 51 62](tel:+905425525162)