Automation · Orders and fulfillment

Quote and ship an Andreani parcel over WhatsApp without creating a wrong order

An AI agent quotes on your Andreani contract, offers a branch or pickup point, validates the address and creates the shipment only after an explicit yes.

Show me this with my own operation See every automation

How do I quote and ship an Andreani parcel from WhatsApp without creating the wrong order?

A Met connected to Andreani first asks whether the parcel goes to a home address or to a branch, because those are two contracts with two prices, and quotes on your contract with the real parcels. If the person prefers to pick it up, it shows the branches and pickup points that serve their postal code. Before shipping it validates the address against Andreani and resolves the province code. With origin, destination, parcels and price on screen it waits for an explicit yes and only then creates the order, because Andreani does not allow cancelling it over the API. It leaves the label link in an internal note for whoever ships, and when someone asks where the parcel is, it only claims delivery from the order status.

Where it applies: Argentina. Andreani operates in Argentina and the rate comes from each merchant's contract: one for home delivery and another for branch or pickup point.

What starts it

When the customer writes

It starts when a buyer writes over WhatsApp to ask what shipping to their postal code costs, where they can pick up, or where their parcel is. There is no trigger to set up: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Sales Met that closes with shipping

This is not a named, seeded Met. It is the Met that already answers the store's WhatsApp, with Andreani connected. Its job is to make sure the shipping price the buyer hears is your contract price and that the order created is exactly the one the person approved.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

Andreani Run stores and orders
Meteor CRM Sell and serve

6 steps · 10 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Ask for the delivery mode before quoting

Home delivery and branch delivery are two different contract numbers with different prices. Picking the wrong one does not raise an error, it returns a wrong price, so the Met asks for the mode when it is unclear. It then quotes with the destination postal code and the parcels, with their weight or measurements and the declared value that sets the insurance. The price it shares is the one Andreani returned, together with the mode used; it does not recalculate it or add anything.
- andreani_cotizar_envio Andreani
2
Offer the branch or pickup point that is actually close

If the person prefers to pick up, the Met uses their postal code to find Andreani branches, with address, opening hours and coordinates, plus third party pickup points, which usually stay open longer. The pickup point search needs the branch contract. The person chooses in the chat and that choice travels into the order.
- andreani_buscar_sucursales Andreani
- andreani_buscar_puntos_de_tercero Andreani
3
Validate the address and resolve the province

For home delivery, the Met validates street, number, locality, province and postal code against Andreani and gets latitude and longitude back. If the address does not resolve, it confirms it with the person before going on. Order creation requires the province as a code, for example AR-B, not as a name: the code comes from the province list, because writing the name makes the order fail.
- andreani_validar_direccion Andreani
- andreani_consultar_provincias Andreani
4
Create the order only after an explicit yes

The Met shows origin, destination, recipient, parcels and the quoted price, and waits for the buyer to approve those details. The creation tool requires the confirmation flag set to true and rejects the call without it, because an order created by mistake cannot be cancelled anywhere. With the yes, it sends the order on the contract for the chosen mode and returns the shipment number, noting that from then on it can no longer be cancelled.
- andreani_crear_orden Andreani
5
Leave the label for whoever ships, not for the buyer

The connector stores the label PDF in Meteor private storage and returns a signed link that expires after seven days. Because the label carries the recipient's name and address, the Met does not send it to the buyer's chat: it leaves the shipment number and the link in an internal contact note, where your team opens it to print. If the link could not be generated, it says so instead of making one up.
- andreani_obtener_etiqueta Andreani
- crm_add_note Meteor CRM
6
Answer where the parcel is without guessing delivery

With the shipment number, the Met returns the tracking events with date, status and the branch where each happened. To claim something was delivered it checks the order, which holds the real status: the newer Andreani tracking does not emit the delivery event, and events stopping is not information. The recipient's personal data comes trimmed, and this answer does not need it.
- andreani_rastrear_envio Andreani
- andreani_consultar_orden Andreani

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Andreani API username, password and client code

Andreani issues them when you sign your contract; they do not come from a Meteor agreement. They are loaded in the workspace, and the sandbox pair and the production pair are different. The connector starts out pointing at the sandbox.
Both contract numbers, home and branch

Andreani issues one per delivery mode. Without the home contract you cannot quote home delivery, and without the branch contract you cannot search third party pickup points. The connector names the missing one instead of saying the integration does not work.
A WhatsApp line with the Met assigned and the Meteor CRM

The store connects its WhatsApp Business API line and assigns the Met that answers buyers. The Meteor CRM is included and is where the internal note with the label link lives.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not cancel or void an order. Andreani does not expose that operation over the API: anything created by mistake is settled with the carrier, which is why creation waits for an explicit yes.
It does not compute freight or chargeable weight. If the quote fails, the Met says it could not quote; it does not estimate a price to avoid leaving the question open.
It does not send the label to the buyer. The signed link carries printed personal data, expires after seven days and is for whoever ships, not for forwarding.
It does not work outside Argentina. It quotes by Argentine postal code, validates Argentine addresses and the rate currency is the Argentine peso.
It does not book a pickup or print on its own. It delivers the shipment number and the label link; handing the parcel in at a branch or arranging a pickup is up to your team and Andreani.
It has not been tested end to end with a real contract. The connector was exercised against the sandbox without contract credentials: nobody has confirmed yet that Andreani accepts the order as it is sent, and the province list may not respond in that environment. Create a test order before serving buyers.

FAQ

Questions about this automation

Because they are two contracts with different rates. Quoting on the wrong contract does not fail: it returns a price that is not yours, and that is the one the buyer would remember. If the buyer switches mode, the Met quotes again instead of adjusting the number.

Not without the confirmation. The tool rejects creation unless the confirmation arrives as true, and the Met sets it after the buyer approves in the chat the details it showed. The tool requires that flag but cannot check the yes on its own, and in this procedure the yes comes from the buyer, not from someone on your team. It is the only write in this procedure and it works that way because Andreani does not allow cancelling over the API.

Yes. The connector starts in the Andreani sandbox, with its own username and password. There you can quote and create test orders; a sandbox number does not exist in production, and the other way around.

From the order status. Tracking is good for telling the journey, but its newer version does not emit the delivery event, so the Met never infers it from events stopping.

Keep going