Sales & orders
Customers ask for a product by text, photo or voice message, see the price and order on WhatsApp.
- Stock and prices come from your software
- Customer-specific prices and discounts
- Approved orders arrive in your software as sales orders
Your customers write on WhatsApp; Meta Reva reads the answer from SAP Business One for small and mid-sized companies and replies in seconds. Stock, price and account information is read from SAP Business One; records are written back only where the access path and your permissions allow it.
Each one reads live data from SAP Business One. You choose where to start.
Customers ask for a product by text, photo or voice message, see the price and order on WhatsApp.
Customers ask what they owe, and their account statement arrives on WhatsApp as a PDF.
Recurring questions are answered automatically; the rest go to your team.
A daily summary of sales, collections and stock arrives on your phone.
What we look at first: which edition you run and which access path it offers.
We identify your SAP Business One version and database (SQL Server or HANA). We check whether the Service Layer is installed and which OData version it offers.
The Service Layer is usually chosen for WhatsApp; SQLQuery or SQL views may suit bulk reports. The choice follows the route your installation offers.
A separate SAP user with read-only authorization is defined. Business partners, orders and items are tried with small queries.
The Service Layer is published only over TLS and a restricted network path. The session is reused, query volume is limited, and license scope is confirmed with your partner.
Read the general guide: how to connect WhatsApp to ERP software
Meta Reva is an independent software company and is not an official partner of the vendor. Product names belong to their owners.
The most common questions about setup, software and security.
The Service Layer is SAP's REST/OData-based access route and is usually the best fit for a web-based layer. The DI API is an alternative, but it suits local Windows applications better.
The Service Layer works on both databases. However, exposing SQL views as OData is specific to the SQL Server edition, and separate SQL may be needed for each.
The Service Layer supports OData aggregation and grouping options. For calculated balance fields, version and database support should be tested first.
A session is opened with user and company database details and expires after a set time. The session is therefore reused and renewed when it expires.
The customer is told that the information is not available right now and the conversation is handed to your team. No answer is made up from old data.
A single flow (for example stock and price enquiries) is usually live within days; wider setups are added step by step. Setup is remote, anywhere in Turkey.
Tell us which software you use and what customers ask most. We will map out the right flow for free.
We only use essential browser storage to run this site. With your permission we measure how the site is used with analytics tools. Details: Cookie Policy · Privacy Policy.
Choose which cookies you allow. You can change this at any time from the “Privacy preferences” link at the bottom of the page.