• CREATING AND MANAGING FORMS • SETUP GUIDE

Understanding Form Names, Slugs, and Statuses

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Use the form name for admin organization, the slug for storefront placement, and form status to control whether a registration form is published.

Before you begin

Identify the form by both its internal name and slug before making changes. Check where that slug is used on your storefront, and review dependent rules or mappings before removing questions.

Name, slug, and status have different jobs

The form name is an admin label. The slug is the identifier entered in the Wholesale form block. The optional visible title is what applicants see above the questions. These values serve different purposes and do not need to be identical.

Draft is for preparation, Active is the published state shown by the current interface, and Archived retains a form you no longer want to use for new applications. An active form still needs storefront placement; status alone does not create a page.

Reference and examples

Setting Purpose Example
Internal name Identify the form in admin Retailer applications
Slug Select the form in a theme block retailer-applications
Visible title Introduce the storefront questions Apply to become a stockist
Draft Preparation before activation Questions still under review
Active Published form ready for placement Saved and tested form
Archived Retained but retired form Previous program

Example

Use an internal name of Demo Retailer Application and slug demo-retailer. Keep it Draft during setup, then activate it and enter demo-retailer in its app block.

Expected result

The block loads the intended active form; changing the internal name does not replace the need for the correct slug.

Limits and important behavior

  • A form’s admin name is separate from an optional visible form title.
  • Publishing does not add the theme block automatically.
  • Do not delete a form solely to pause it when an archive option fits your needs.

Troubleshooting and verification

If the correct name appears in admin but a different form loads online, compare slugs rather than names. After changing a slug, update each block that refers to it. Draft or archived forms should not be relied on as live application placements.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Form Names, Slugs, and Statuses”. Include the relevant saved settings and the example outcome so readers can connect the explanation to the interface. Use dummy applicant details and mask any secrets.

Related guides