Skip to main content

5. Marketplace: Configurations

The Marketplace → Configurations page lets you set up all your Marketplace lookup‐lists—like order statuses, payment methods, and product categories—on a per-project basis. Each project has its own entries, but you can save time by clicking Clone from project to import another project’s configuration in one step.

1. Navigating to Configurations

Open the side menu → Marketplace → Configurations.


At the very top of the Configurations page you’ll find the Settings by project bar. This is your single-click switcher for viewing or editing any project’s lookup lists:

  1. Search – Filter the pill list by typing part of a project’s name.

  2. Project pills – Click a pill to load that project’s configuration panels below.

  3. Horizontal scroll – If you have many projects, scroll left/right to reveal hidden pills.

Below the project selector, you’ll see Order statuses.

For example:

Order statuses
(If none exist yet) “No data to display”

2. Adding a New Order

Click + Add on the Order statuses card.


Fill in the Add order panel fields:

    1. Project: (pre-selected) the target project.
    2. Name: Internal key (e.g. pending).
    3. Label: What users will see (e.g. Pending).
    4. Color picker: Choose the badge color for quick recognition.
    5. Make as default: Sets this status as the default when new orders are created.
    6. Final: Marks this status as a terminal (can’t transition onward).

Click Save to create the new status.

3. Editing & Deleting Items

Once a status exists, use the ✏️ Edit icon to change its Name, Label, Color, or flags, and the 🗑️ Delete icon to remove it.


4. Cloning from Another ProjectProject:

  1. Click Clone from project.

  2. In the modal, pick the source project whose items you want to copy.

  3. Click Clone.

  4. All statuses from that project instantly appear in your current project’s list.

5. Best Practices

  • Clone an existing project’s statuses to keep workflows consistent.

  • Use Default sparingly—only one status should be the entry point.

  • Mark Final statuses (e.g. Completed, Cancelled) so downstream logic can trigger correctly.

  • Review and prune unused statuses to avoid clutter.

By combining project‐scoped lists, easy cloning, and a simple add/edit/delete workflow, the Configurations module ensures that each project’s unique needs are met while minimizing repetitive setup.
Back to top