Integrating Dux with WhatsApp: what its API does and who connects it

What is possible today between Dux and WhatsApp

Integrating Dux — one of the management systems most used by small businesses in Argentina — with WhatsApp means two very different things, and it pays to separate them before going further.

The first already ships with the system. From a recorded sale you hit share, pick WhatsApp, and the chat opens with the receipt. It works, and it is manual: somebody on your team has to be there, with the sale open.

The second is your Dux catalogue answering on its own inside the conversation. So that when the customer asks the price of a product, the answer comes out of your system and not out of somebody's memory. That second one goes through the API, and it is the one almost nobody explains.

What the Dux API documentation says

Dux writes it in its own guide, and it is worth quoting because it is more specific than you would expect.

With the API "it is possible to create orders, check prices and stock", as well as access "much of the information managed in Dux Software". Those are exactly the three operations automated customer service needs: knowing what it costs, knowing whether there is any, and leaving the order recorded.

It also spells out who it is for: "The Dux API is intended for developers or people with programming knowledge." It is not a checkbox you tick on a settings screen.

What "the integration is external development" means

That is the sentence that decides everything else, and it is also in the official guide: "Integration via API is development external to the Dux Software system."

Translated: Dux gives you the door, the documentation and the key. It does not walk through the door for you. Its recommendation is to consult external consultants specialised in that kind of development.

That is why the search leaves you halfway. You have an ERP publishing a full API, and on the other side there is nothing using it to serve your customer. The work exists and has to be done, or bought already built.

What changes when the Dux catalogue enters the conversation

What changes is who answers the usual questions, and where the number comes from.

Your synced catalogue stops being a list somebody looks things up in and becomes something the conversation can read. The customer writes "something waterproof for the rain" and the search lands on the right product, even without the exact name or the code.

That is the difference between searching by word and searching by what the person meant. Most of your customers do not know the SKU of anything.

Where the price your customer sees comes from

It comes from your system, and that is the only acceptable answer.

An improvised price is a problem discovered late: the customer saves it, quotes it, and complains about it. When the price comes from the catalogue, the conversation repeats the number already loaded, not one that resembles it.

And there is a detail that pays off months later. The order stores the name and the price as they were on the day of the sale. If you update the list tomorrow, the old order still says what was sold and for how much.

When stock gets checked, and what happens if Dux does not answer

Stock is checked before the order is confirmed, not before the product is shown.

Situation	What happens in the conversation
Everything is in stock	The order is confirmed and recorded
There is less than requested	How much there is gets stated, item by item, and the customer decides
The system cannot be reached	Availability is reported as unknown and it waits
The product is discontinued	It stops being offered, and an old order still resolves to that product

The third row is the most ignored and the one that matters most. When the ERP does not answer, the temptation is to say "yes, we have it" and sort it out later. That turns a five-minute outage into an order you cannot fulfil.

How it gets connected, with no ticket and no waiting

From the panel, in four steps, without writing code.

1. Pick the provider. Dux is the first one supported; the rest get added one at a time.
2. Enter your credentials. They are stored encrypted and never returned.
3. Look at the preview. Real products from your account get pulled in and you see how they map.
4. Switch it on. Only then does the catalogue enter the conversation.

Step 3 is what avoids the 3 a.m. call. A mistyped password or a field that cannot be read shows up as a problem now, with sync switched off, and not on the night a customer asks a price.

How often it syncs and how to force it

You pick the frequency from a short list, sized by what your system can take.

The floor of that list is not set by us: it is set by your own provider's request limit. You can go all the way down to switching automatic sync off and syncing only when you say so.

Just changed a price? There is a "sync now" that does not wait for the next run. And if a sync fails, or products stop arriving, we tell you. And ourselves.

Key takeaways

• Dux already publishes an API that allows creating orders and checking prices and stock. The door is open.
• The same documentation makes two things clear: it is for profiles with programming knowledge, and the integration is development external to Dux.
• What comes up when you search "Dux and WhatsApp" is the manual sharing of receipts. That is a different thing.
• Once connected, the catalogue answers prices from your system, checks stock at order confirmation and stores the price on the day of the sale.
• The connection is made from the panel, with a preview of what will be imported before anything is switched on.
• Today Dux is the first supported system. The rest get added one at a time.