Eqolux

Documents the tables run_sql_query can read (orders, documents, products, organizations, categories, tags, supplier profiles, reference lists): every column, the units, how amounts are converted and signed, and example queries.

describe_data

Lists the Eqolux organizations (restaurant or hotel groups) the signed-in user belongs to, with the id that run_sql_query takes.

list_organizations

Runs one read-only PostgreSQL SELECT query on the purchasing data of one Eqolux organization and returns the rows (at most 500, 20 s maximum). The query reads the Eqolux purchasing dataset: orders, documents, products, organizations, product_tags, tags, item_categories, item_category_assignments, supplier_profiles, supplier_contacts, supplier_documents, supplier_document_types, organization_labels, organization_tags, labels, origins, currencies, agribalyse, agribalyse_sub_groups. Every table only contains what the user is allowed to see. describe_data documents each table and column. Main joins: orders.product_id = products.id, orders.supplier_id = organizations.id, orders.client_id = organizations.id, orders.document_id = documents.id. Amounts are already converted to display_currency and credit notes are negative in totals. Spend totals as shown in the Eqolux app are SUM(documents.total_amount_ht); orders holds the product-level detail. Only SELECT statements over these tables are accepted; common SQL functions (aggregates, window functions, date, text, json) are available.

run_sql_query