Antylogic
DemoApp login

399 operational guides

Docs sections
DocsCatalogue setup
Device

How to copy a catalogue

Create a new catalogue from an existing one without editing the source. In the GB demo, Harbor Soho can copy Soho Menu, review the prefilled create form, rename the draft and save it as a separate catalogue in the current scope.

In this article

Use this flow when a restaurant wants to reuse a proven menu structure for another service, location context or operational test without rebuilding the catalogue from scratch.

Copying is a create flow. Antylogic loads the source catalogue through `copyFromId`, fills the normal Create Catalog form, and only creates a new record when the operator submits a valid changed draft.

Before you start

  • A readable source catalogue exists; in the GB demo use Harbor Demo Group, Harbor Soho and `SETUP_CATALOG_SOURCE_NAME=Soho Menu`.
  • The session has an organisation selected. For the location flow, `LOCATION_ID` must also be selected or present in the route.
  • The operator has `catalog:view` to load the list and source catalogue, and `catalog:manage` to see Copy and create the new catalogue.
  • Copied `product_ids` and `product_type_ids` belong to the exact destination scope. If the source is inherited from another scope, review products and type order before saving.

Instructions

  1. 1.

    Open the catalogue list

    Go to the Catalogues tab for Harbor Soho and filter for Soho Menu if needed. The same copy action is available from the organisation catalogue list when working at organisation level.

  2. 2.

    Start from Copy

    Open the row actions for Soho Menu and choose Copy. Antylogic opens Create Catalog with `copyFromId` pointing to the source, so the original catalogue is not edited.

  3. 3.

    Review the prefilled draft

    Check the copied name, the Default toggle, the reused image reference, selected products and Product type order. The copied suffix is currently shown as `(copia)`, even in the English demo context.

  4. 4.

    Rename or adjust the catalogue

    Make at least one valid change before submitting. The safest first change is a unique name that identifies the new service, shift or intended use.

  5. 5.

    Check products and type order

    Review the Products section before creating the copy. Keep only products and product types that belong to the destination scope, especially when copying a catalogue that was visible because it was inherited.

  6. 6.

    Create and verify

    Submit the form to create the new catalogue. Antylogic posts the normal create payload, shows the creation notification and returns to the Catalogues tab where the copied catalogue can be found.

Validations and limits

  • Copy is available only when the current scope grants `catalog:manage`; loading the list and source catalogue requires `catalog:view`.
  • There is no separate backend copy endpoint: the UI loads the source and sends the normal catalogue create payload.
  • Name is required after trimming whitespace, and a duplicate catalogue name in the same organisation or location scope is rejected.
  • The submit action stays disabled until the form is valid, dirty and not submitting; a freshly opened copy can therefore require a rename or another change.
  • Default is forced off when the copy draft is initialised, and organisation-level catalogues cannot be created as default.
  • Copied products and product types are normalised, deduplicated and validated against the exact destination scope.
  • Copying reuses products, product type order and `image_file_id`; it does not clone products, product types or image files.

Expected result

A separate catalogue is created in the current organisation or location scope. Soho Menu remains unchanged, while the new catalogue reuses the selected products, product type order and image reference unless the operator changed them.

Related articles