Messages are useful for selling, not for reporting
A DM thread can hold the product name, delivery address, price negotiation and proof of payment. It does not naturally answer how many units remain, which orders are unpaid or what sold last month. Searching conversations also makes a growing business depend on memory and one account.
Once the customer confirms, create the structured sale. Keep the messaging app as the communication channel and Salelog as the operational record.
A simple message-to-sale workflow
Before the conversation, you can share a product catalog link so customers can browse selected products and photos without creating an account. Prepare it in the mobile app with an active Plus or Pro plan. Choose whether prices and contact details appear; the catalog does not expose internal stock quantities or take orders automatically.
- Confirm product, quantity, price and delivery details with the customer.
- Check the correct inventory location.
- Create or select the customer in Salelog.
- Record the sale with the agreed items.
- Record payment now or leave the appropriate balance open.
- Handle shipping or delivery in the external service you use.
If an order is cancelled, cancel the transaction rather than deleting evidence and manually adding stock back.
Avoid double-selling across channels
Without an automatic connector, a sale on one channel is not known to another until you record it. Enter confirmed orders promptly and keep one operational source of quantity. If volume becomes too high for manual recording, that is a real requirement for an ecommerce synchronization platform, not a reason to pretend the connection exists.
Separate sales from money received
A screenshot of a transfer is not the same as a recorded receipt, and a partial payment is not a second sale. Keeping these events separate lets the customer balance tell a coherent story even when the conversation spans several days.