Back to home

Data export: structure and formats

Last updated: 29 October 2026 · Version: 1.0

Courtesy translation. This English translation is provided for convenience only. Only the Spanish version is legally binding and it prevails in the event of any discrepancy: read the Spanish version.

1. What this page describes

This page describes the file generated by the Settings → Profile → “Download my data (GDPR)” option of Scandallo: which files it contains, in which formats and with what structure and fields. It is the up-to-date description of the structures and formats of the exportable data referred to in Article 26(b) of Regulation (EU) 2023/2854 (Data Act) and, together with the download itself, the open export interface of section 17.4 of the Terms and Conditions of Use, available free of charge to the Customer and to the destination providers that the Customer authorises.

Scandallo is a trade name of DELAMAR A SU RESTAURANTE, S.L. (sociedad unipersonal), NIF B11969672.


2. How to obtain it

  • Where: in the app, Settings → Profile → “Download my data (GDPR)”, while signed in.
  • Cost: none. It can be downloaded at any time, up to 5 times per hour.
  • What data it includes:
    • if you are the owner of an account, the data of your account and of all the venues you own;
    • if you are part of another business's team (Authorised User), only your personal data (account, profile, memberships, messages and surveys), not the data of the business you work in.
  • For another provider: the Customer may hand the file over to the destination provider of its choice or ask for help with the transfer through the channels in section 9 of this page (section 17 of the Terms and Conditions of Use).

3. Contents of the file

The download is a compressed ZIP file named scandallo-my-data-YYYY-MM-DD.zip (the date is the date of the download) that contains three files. The file names follow the language in which the app is used; in Spanish they are scandallo-mis-datos-AAAA-MM-DD.zip, datos.json, ficheros.html and LEEME.txt, as in the Spanish version of this page. The content of data.json (datos.json) is the same in both languages:

FileFormatContents
data.jsonJSON (RFC 8259), UTF-8 encoded.All the data in the download, with the structure in section 4.
files.htmlHTML page, UTF-8 encoded, which opens in any browser.Links to download the files that the Service keeps: invoice images and PDFs, dish photos and profile photo, grouped by venue. The links are valid for 2 days (48 hours); after that, simply download the data again, which generates new links. Each file is downloaded in the format in which the Service keeps it (image or PDF).
README.txtPlain text, UTF-8 encoded.Explanation of the contents, date of the download, number of venues included, what is not included (section 7) and, if any part could not be read, a notice to repeat the download.

4. Structure of data.json

The file contains a single JSON object with these keys:

KeyTypeContents
formatoTextIdentifier and version of the format. Current value: "Scan-Dallo · exportación completa de la cuenta · v1".
exportado_elDate and timeTime of the download.
cuentaObjectAccount data of the person downloading (see below).
localesList of identifiersIdentifiers (id) of the venues included.
tablasObjectOne key per table (section 6); the value of each one is a list of rows, and each row, an object with its fields.
no_incluidoList of textsWhat is not included in the automatic download and how to request it.
erroresList of textsParts that could not be read in that download (names of tables or of groups of files). Empty if the download is complete.

Fields of the cuenta object:

FieldContents
idIdentifier of the account.
emailSign-in email address.
altaDate and time the account was created.
email_verificado_elDate and time the email address was verified.
ultimo_accesoDate and time of the last sign-in.
metodos_de_accesoThe account's sign-in methods (for example, email or Google).
datos_de_perfilProfile data stored by the authentication system (for example, the name received from Google).

5. Conventions

  • Identifiers: the id field of each row is a unique identifier (UUID, unless otherwise stated).
  • Relationships: fields ending in _id contain the id of the related row: business_id, of the venue (businesses); supplier_id and default_supplier_id, of the supplier (suppliers); ingredient_id, of the ingredient (ingredients); invoice_id and shared_from_invoice_id, of the invoice (invoices); recipe_id and sub_recipe_id, of the recipe or sub-recipe (recipes); folder_id and parent_id, of the folder (folders); count_id, of the stocktake (inventory_counts).
  • Dates: dates with a time follow the ISO 8601 standard, with time zone; dates without a time, the YYYY-MM-DD format; monthly periods (period), the YYYY-MM format.
  • Amounts: in euros, as decimal numbers, except in the payments table, where amount_total and amount_tax are expressed in cents (the smallest unit of the currency, as provided by the payment platform).
  • Empty fields: value null.
  • Structured fields: some fields themselves contain JSON objects or lists (for example, raw_ocr_json, preparation, drink_extras, drink_targets, capabilities or permissions).
  • Files: the image_url, photo_url and avatar_url fields contain the internal path of the file in the Service's storage, not a public link; the file is downloaded from files.html.

6. Tables

The tables of a venue only include the rows of the venues owned by the person downloading. The person's tables only include their own rows. The tables marked as complete are exported with all their fields: if any field is added in the future, it will also appear in the download and will be added to this page.

6.1. Venues and subscription

TableContentsFields
businessesEach venue.id, name, type (type of business), tax_country (country for tax purposes), created_at, onboarding_completed_at, trial_started_at, price_alerts_enabled (email alerts switched on), public_menu_enabled (public menu switched on), stock_updated_at, avatar_url (profile photo), drink_profile and drink_targets (drinks settings).
subscriptionsSubscription of the venue.business_id, status, plan_tier (basico, pro, negocio or max), billing_interval (mensual or anual), trial_end, current_period_end (end of the paid period), monthly_ocr_limit (scans per month), updated_at.
paymentsSubscription payments.business_id, stripe_invoice_id (internal number of the invoice on the payment platform), status, amount_total, amount_tax, currency, paid_at, failed_at, hosted_invoice_url and invoice_pdf (links to the invoice), created_at.
ocr_usageAI scans used each month.business_id, period, count, updated_at.
custom_plan_requests (complete)Custom plan requests made from the app.id, business_id, scans, capabilities, recipes_pref, notes, phone, estimated_price, status, created_at.
custom_plan_grantsCustom plan activated.business_id, capabilities, activated_at.

6.2. Suppliers, ingredients and prices

TableContentsFields
suppliers (complete)Suppliers.id, business_id, name, cif, counts_as_purchase (whether its invoices count as a purchase), created_at.
supplier_product_aliases (complete)Matches between the text of a product on a supplier's invoices and an ingredient.id, business_id, supplier_id, ingredient_id, normalized_text, created_at, updated_at.
ingredients (complete)Ingredients.id, business_id, name, category, base_unit, default_merma_pct (default waste, in %), default_supplier_id, stock_qty (stock), par_min and par_max (minimum and maximum levels), allergens_reviewed_at, created_at.
ingredient_allergens (complete)Allergens of each ingredient.id, business_id, ingredient_id, allergen_code, source (origin of the assignment), created_at.
ingredient_prices (complete)Price history of each ingredient.id, ingredient_id, supplier_id, invoice_id, date, price, quantity, unit, created_at.

6.3. Invoices and folders

TableContentsFields
folders (complete)Folders.id, business_id, name, color, parent_id, position, created_at.
invoices (complete)Invoices and delivery notes.id, business_id, supplier_id, folder_id, numero, date, base (taxable amount), iva (VAT amount), total, status, counts_as_purchase, image_url, raw_ocr_json (result of the AI scanning as it was obtained), shared_from_invoice_id (invoice from another venue that it comes from, if it was copied), created_at.
invoice_lines (complete)Lines of each invoice.id, invoice_id, ingredient_id, raw_text (text of the line), qty, unit, price, quality_flag (scanning quality warning).

6.4. Recipes and costings

TableContentsFields
recipes (complete)Recipes, sub-recipes and food and drink costings.id, business_id, name, category, source, color, n_servings, yield_qty, yield_unit, prep_time_min, preparation (steps), notes, carta_description, on_menu, sale_price, vat_pct, target_food_cost_pct, indirect_pct_on_materials, indirect_fixed_per_serving, escandallo_at (costing activation date), allergens_reviewed_at, photo_url, drink_type, drink_label, glass_ml, drink_extras, created_at, updated_at.
recipe_items (complete)Ingredients and sub-recipes of each recipe.id, recipe_id, ingredient_id, sub_recipe_id, raw_name, net_qty, unit, merma_pct, is_bottle.
recipe_allergen_overrides (complete)Allergens of a dish confirmed or corrected by hand.recipe_id, business_id, allergen_code, present, created_at.

6.5. Sales, stock and costs

TableContentsFields
recipe_sales (complete)Sales of each dish per month.id, business_id, recipe_id, period, units_sold, amount_gross, source, updated_at.
sales_imports (complete)Sales imports from POS files.id, business_id, file_name, source, mode, period, date_from, date_to, generated_at, units_total, amount_gross, created_at.
sales_name_decisions (complete)Answers to “Are these the same dish?” when importing sales.business_id, name_a, name_b, decision, keep_name, created_at.
inventory_counts (complete)Stocktakes.id, business_id, counted_at, note, created_at.
inventory_count_items (complete)Quantities in each stocktake.id, business_id, count_id, ingredient_id, qty, unit.
labor_costs (complete)Staff costs for each month (total amount).id, business_id, period, amount, updated_at.
fixed_expenses (complete)Fixed costs.id, business_id, name, monthly_amount, created_at, updated_at.
trial_surveys (complete)Answers to the Free plan survey.id, business_id, rating, most_useful, missing, blocker, suggestions, created_at.

6.6. The person's data

TableContentsFields
profilesProfile of the person downloading.id, business_id (active venue), role, full_name, created_at, tour_completed_at.
user_businessesVenues to which the person downloading belongs.business_id, role, status, permissions, job_title (job title), display_name, approved_at, created_at.
feedbackMessages sent from “Help & reviews”.business_id, message, page, created_at.
satisfaction_surveysSatisfaction survey.business_id, status, next_ask_at, snoozed_count, rating, recommend, most_useful, suggestion, plan, answered_at, created_at.

7. What the automatic download does not include

  • Security logs (access attempts, request limits), which are deleted after 90 days, and temporary copies of the AI scans (30 days at most), whose content matches that of the invoices. They are provided on request, insofar as this does not compromise the security of the Service (section 17.5 of the Terms and Conditions of Use).
  • Data of each venue's team: the team members, their job titles and permissions, the invitations and the team activity log. Also the names of the recipes' colour labels and the team's default permissions. The owner may request them and they are provided free of charge.
  • Internal security data: the customer and subscription identifiers on the payment platform and the code of the public menu link, which can be viewed in the app.
  • Files that the Service does not keep: of multi-page invoices only the first page is kept, and of electronic invoices imported in XML the extracted data is kept, but not the XML file.

8. Changes to the format

The formato field indicates the version of the structure. If the structure changes (for example, because a table or a field is added), this page is updated with its date. If the Customer needs the data in a single package, in another commonly used format or with help to load it into another service, it may request this free of charge through the channels in section 9.


9. Contact

Requests for switching providers and for data retrieval are governed by section 17 of the Terms and Conditions of Use.