Catalog Management (PIM)

Catalog Manager - Dashboard

Catalog Manager – Dashboard

Catalog Management (“Catalog” or “PIM”), is a full product information management system that can be used to organize product and catalog information. The component can be separated into three parts:

1. Product, Category and Catalog management Management of product information, catalogs and categories, including their relation between one another, start and expiry dates and respective features.
2. Prices and Promotions Management of Generic Price Rules in addition to individual product prices, as well as promotions, which can affect the overall order or product prices.
3. Store Management Management of web stores, the digital equivalent of a website with store functionality. Maps directly into the shop component and allows for a multi-store setup. Each store can be assigned to an individual company, limited to geo ids, have its own theme, email settings, and various behavior configurations (how inventories are handled, which currency to use by default, how up-sells are used, if cart information are stored in cookie etc.).

The component is interconnected with a warehouse management component (facility), which manages the stock information, shipping & shipping gateways, picking / packing and more.

Overall, the application is categorized as follows:

1. Catalogs
   1. Catalog
   2. Catalog Categories
   3. Catalog Parties
2. Categories
   1. Category
   2. Category Associations
   3. Category Content
   4. Category Products
3. Prices (Global Price Rules)
4. Products
   1. Search
   2. Product Information
      1. Associations
      2. Attributes
      3. Categories
      4. Content
      5. Costs
      6. Features
         1. Feature
         2. Feature Category
         3. Feature Group
         4. Feature Interaction
         5. Feature Type
      7. Geos
      8. IDs
      9. Payment Types
      10. Prices
      11. Product
      12. Product Overview
      13. Subscription Resources
      14. Suppliers
      15. Vendors
      16. Warehouses
5. Promotions
6. Stores
   1. Overview
   2. Webstore
      1. Catalogs
      2. Emails
      3. Fin Accts
      4. Keyword
      5. Payment Methods
      6. Promos
      7. Role(s)
      8. Segments
      9. Shipping
      10. Shipping Estimates
      11. Store
      12. Surveys
      13. Vendor Payments
      14. Vendor Shipments
      15. Warehouse
      16. Web Sites

The application in 4.0#

scipio-erp-catalog-manager

The catalog manager in 4.0: the catalogs, the category tree and the products behind the web store.

Do it with an agent#

The catalog ships an MCP server. Point your agent at the catalog webapp and it builds the assortment with you.

claude mcp add --transport http scipio-catalog "https://<host>/catalog/mcp" --header "Authorization: Bearer <token>"

Two tools carry the application. Every call names the tool and one action.

• product — create, update, find, get, import, price_set, variant_add, assoc_set, feature_create, feature_apply, identification_set, content_set, category_create, category_assign, category_child_add, category_list, catalog_create, catalog_category_add, facility_set.
• store — catalog_add, shipment_method_add, shipment_estimate_create, payment_setting_add, promo_create, promo_apply, promo_code_create.

Add a product with its variants#

“Create the product Trail Jacket, add the sizes S, M and L as variants, set the list price to 149 EUR and put it in the Outdoor category.”

The agent calls product:create, product:variant_add per size, product:price_set and product:category_assign. Ask it to read the product back with product:get before you publish.

Import a supplier sheet#

“Here is the supplier’s price list. Import the rows as products and put them under the category they name.”

The agent calls product:import once per batch. The import answers with the rows it rejected, so you correct the sheet and run it again.

Run a promotion#

“Give SCIPIO Shop a 10 percent promotion on the Outdoor category for December and make one code for the newsletter.”

The agent calls store:promo_create, store:promo_apply and store:promo_code_create.

The token is a user login. The agent does what that user may do, and nothing more. Every call writes one audit row. Read the security model before you hand a token out.