--- title: Choosing between record producers and catalog items description: Both the record producer and standard catalog item in App Engine Studio \(AES\) create experiences where users can submit requests through a service portal. However, record producers are more extensible, and enable users to create a record in any table. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/application-development/app-engine-studio/record-producer-vs-catalog-item.html release: australia product: App Engine Studio classification: app-engine-studio topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Add an experience, Enhance your app, Build, App Engine Studio, Building low-code applications, Developing your application, Building applications] --- # Choosing between record producers and catalog items Both the record producer and standard catalog item in App Engine Studio \(AES\) create experiences where users can submit requests through a service portal. However, record producers are more extensible, and enable users to create a record in any table. ## Consider the level of customization Record producers allow for more customization, making the most of the App Engine tools to build experiences from scratch. Catalog items represent services or items a user can request. The catalog of all items is called the Service Catalog, and is part of Service Catalog Management. ## Comparison of record producers and standard catalog items
| Functional area | Record producer | Catalog item |
|---|---|---|
| Purpose | Create custom fulfillment experiences using App Engine automation tools. | Support simple request management applications for which a predefined approval and qualification process exists, such as requesting IT hardware and software. |
| Extensibility | Customizable. | Pre-defined. |
| Example | Password reset form that creates a password reset request. | Form to request a parking permit. |
| Development model | Process is as follows:1. Set up a business-focused data model. 2. Define the kind of experience your users will leverage. 3. Define the automation or business logic. 4. Define the user roles that will use the app. | Catalog items heavily rely on the request fulfillment process for fulfilling items defined in Service Catalog, a central, accurate, and consistent source of data. |
| Reporting | Easier to create dashboards with a purpose-built data model. | Requires creating database views and scripting to gather variables into other tables to configure specific reports. |
| Scalability | Business-focused app makes it easier to find resources and make app changes in a low-code environment. | Typically part of a Service Catalog Management operation with a dedicated team managing each catalog. |
| Security | Scoped apps allow flexibility to manage permissions without being an administrator. | Catalog items are typically built in a specific scope, and less flexible. |