Integration · Run stores and orders
Fudo API: technical scope pending approval
Technical scope studied for the Fudo API: menu, tables and dine in orders. Meteor is not an approved Fudo integration and does not offer it today.
How does Fudo connect to Meteor?
This page describes a technical Meteor connector built against Fudo's public OpenAPI. It is not official Fudo documentation, an approved integration or a feature available for purchase. Meteor does not appear on Fudo's published official partner list. The code covers 7 tools that read the menu and tables, create and extend dine in orders and return the status of every dish. It does not cover delivery, takeaway, payments or till operations. Fudo says its general public API is included with the Pro plan, but limits own-site connections to the restaurant's single-use development with no intermediaries and warns that integrations offered outside its list are not approved. No credentials will be connected and no implementation is promised until Fudo authorizes or approves it and the contract is validated with a real account.
Studied scope
What the technical Fudo connector covers
Designed scope: from the conversation to the kitchen
The code looks up each product on the menu, takes the dining room table and creates the order with its lines to avoid manual retyping. This is the scope implemented in the connector; it does not mean Meteor is approved by Fudo or can connect a customer account today.
The price comes from the card, not from the model
In the technical design, every dish is loaded by its Fudo id and the amount comes from the product stored there. The model does not calculate or round totals, and when a search finds nothing the tool returns a warning instead of inviting it to make something up.
Answering how is my order doing, dish by dish
The query tool reads the status of every line: pending, being prepared, ready or served. That is the detail the design would give the agent instead of reducing an order to one "in progress" label that hides dishes moving at different speeds.
The customer asked for something else
The design can add lines to an open order, with a note for the kitchen when needed, without creating a second sale on the same table. It remains limited to dine in service and subject to Fudo's authorization before any real use.
Finding the order when nobody remembers its number
The tool lists open orders, newest first, so the design can locate a sale by table and time before reading it or adding anything to it.
7 tools
Tools implemented in the Fudo connector
These are code capabilities, not a customer integration until Fudo grants authorization.
| Tool | What it does |
|---|---|
fudo_listar_categorias | Lists the menu categories, such as starters, mains and drinks, with their order on the card and the kitchen each one is sent to. |
fudo_buscar_productos | Searches dishes and drinks by name or by category and returns their id, their price and whether they are active on the card. It is where the id the order needs comes from. |
fudo_listar_mesas | Lists the tables with their number and their room, and flags which ones have an open sale whenever Fudo returns that detail. |
fudo_crear_comanda | Opens the dine in order on a table and loads the dishes onto it, which is what makes the food reach the kitchen. It requires the table and the number of guests. |
fudo_agregar_a_comanda | Adds dishes to an order that is already open, for when the customer asks for something else. |
fudo_consultar_pedido | Returns the status of an order, its total, its table and how each dish is doing in the kitchen: pending, being prepared, ready or served. |
fudo_listar_pedidos_abiertos | Lists the orders currently in progress, newest first, to find the one for a table when you do not have its id. |
The limits
What the Fudo integration does NOT do
We would rather say it here than have you find out during rollout.
-
It is not an approved integration or available for purchase. Meteor does not appear on Fudo's official partner list; Fudo warns that it does not support or take responsibility for integrations offered outside that list.
-
It does not take delivery or takeaway orders. This Fudo API only accepts dine in sales and requires a table; orders that leave the venue live in a different Fudo API that is not integrated.
-
It does not settle the bill or close the till. None of the seven tools touches payments, tips, payment methods or the end of shift: the order comes in through here and the money is still handled in Fudo.
-
It does not invent the detail of an order. When the Fudo response does not carry the lines, the tool returns their ids and says the detail has to be checked in the local system, instead of filling in with dishes nobody ordered.
-
It does not give a kitchen status for the whole order. The fine grained status lives on each line, so one order can have a dish already served and another not started: it is answered line by line, not with a single status that would average two different things.
-
It does not edit the menu. It reads products, prices and categories exactly as they are loaded in Fudo, but it does not create dishes, does not change amounts and does not switch anything on the card on or off.
-
It does not void or fix a line that is already loaded. A dish that went in wrong is removed from Fudo by a person: the connector does not expose the void, and an order that reached the kitchen has already moved real work.
-
It does not book tables or always claim which ones are busy. It flags occupancy only when Fudo returns the active sales along with the tables, and when it does not return them it says so instead of guessing.
-
It does not bring responses confirmed against a real account. The contract came from the public Fudo OpenAPI document and the transport is verified by probing, but Fudo offers no test environment, so the exact shape of each response is confirmed with the first venue that uses it.
Before you start
What you need to connect Fudo
- 1
Fudo authorization or approval before any connection
Meteor does not currently appear on the official partner list. Fudo limits own-site connections to a restaurant's single-use development with no intermediaries and warns about unapproved integrations. Until Fudo authorizes this case or approves Meteor, the connection is not offered and customer credentials are not requested.
- 2
Pro plan and credentials issued by Fudo, after authorization
Fudo says its general-purpose public API is included with the Pro plan. The account and its permissions remain subject to Fudo's conditions; having the Pro plan does not by itself make an intermediary an approved integration.
- 3
A Fudo user dedicated to the API
You create it in your Fudo panel, for example api@yourrestaurant. What your Met can do is exactly the permissions of that user role, so a narrow role shows up as a refusal when the order is created, not when the connection is made.
- 4
The dining room and the menu loaded in Fudo
The order requires the table and the id of every product, and both come from Fudo. If the tables or the card are not loaded, there is nothing the connector can make up in their place.
Frequently asked questions
Questions about Fudo and Meteor
No. Meteor does not appear on Fudo's published official partner list. This page documents code and technical scope, not an available integration. No real account will be connected and no implementation will be offered without Fudo's authorization or approval.
No. Through this API Fudo only accepts dine in sales, and it also requires a table, so the connector covers that and nothing else. Orders that leave the venue are handled in a different Fudo API that is not integrated, and promising it would be selling something that does not exist.
No, and the connector settles it. Every line is loaded by the product id in Fudo, so the amount comes from the card. If the search finds nothing, the tool returns an explicit warning instead of an empty list, so that your Met says it is not on the menu rather than improvising.
Dishes are loaded one by one and the connector does not stop at the first failure: if three go in and one fails, the order is left incomplete and the response says exactly that, with the list of what went in and what did not. Your Met cannot confirm the whole order to you: it tells you what was loaded and what has to be sorted out at the venue.
No. The connector opens the order, loads dishes onto it and checks how it is doing, but it does not charge, does not record tips and does not close the till. That is still done in Fudo, by a person, and it is deliberate: moving money with nobody in the loop is not what this connector solves.
Because it is the only status that helps whoever is waiting. The sale has its own coarse status, and a real table is almost never all at the same point: something is served, something is on the grill and something has not started. Returning a single status would hide the very thing the person wants to know.
Not yet, and that is worth saying. Fudo publishes its full contract, which is why every field the connector reads is typed in that document, and the transport was verified by probing. What is missing is the first real account, because Fudo offers no test environment. If part of a response arrives differently, the connector would rather flag it than fill it in.
Step by step
Automations that use Fudo
Complete tasks, with the steps and the tools that run at each one.
Run stores and orders
Other integrations in the same family
Do you need to assess a Fudo integration?
We first review authorization and approval. We do not request credentials or promise a connection before they are confirmed.