Services

Services are non-physical offerings that suppliers can provide to stores and customers through the Axiom platform. Unlike physical products, services represent work, expertise, or activities that suppliers can offer. The platform provides comprehensive tools for suppliers to create, manage, and sell services alongside their physical products.

The Axiom platform supports two main types of services:

1. Fixed Services: These are services with a fixed price and scope. They are typically one-time services with a predefined cost. Fixed services use "AU" (Arbitrary Unit) as their unit label, and the quantity is typically not specified.

2. Variable Services: These are services where the price may vary based on factors such as time, effort, or other variables. Variable services allow for more flexible pricing models.

Each service in the system has the following key attributes:

• Identifier: A unique identifier for the service within a supplier's catalog
• Name: The name of the service as it appears to customers
• Description: A detailed description of what the service includes
• Type: Whether the service is fixed or variable
• Unit Size: The size of the unit being sold (applicable for variable services)
• Unit Label: The label for the unit (e.g., "hour", "day", "session")
• SKU: Stock Keeping Unit - a unique identifier for the service
• URL: An optional URL with more information about the service
• Group Identifier: An optional identifier to group related services together

Suppliers can create services through:

1. Web Interface: Using the supplier dashboard to create services individually
2. CSV Import: Bulk importing services using a CSV file with the required fields
3. API: Programmatically creating services using the API

When creating a service, suppliers must provide:

• A unique identifier
• Service type (fixed or variable)
• Name
• Unit size and label
• SKU
• UNSPSC code and version (for categorization)

Optional fields include:

• Description
• URL
• Form ID (for associated forms)

Services can be updated to modify their attributes, properties, or related information. Updates can be made through:

1. Web Interface: Editing service details in the supplier dashboard
2. CSV Import: Bulk updating services using a CSV file
3. API: Programmatically updating services using the API

Services can be:

1. Archived: Temporarily removed from active use but retained in the system
2. Permanently Deleted: Completely removed from the system

Archived services can be restored if needed.

Services can have custom properties that provide additional information about the service:

• Properties are key-value pairs (e.g., "Duration": "2 hours")
• Properties can be used for filtering and searching
• Properties can be translated into multiple languages
• Properties are stored with the service and can be updated as needed

Services can include various media to better represent the offering:

1. Image URLs: Images that showcase the service
2. Document URLs: Documents that provide additional information about the service (e.g., brochures, specifications, terms)

Services can have various codes associated with them:

• SKU: The supplier's own stock keeping unit
• UNSPSC: United Nations Standard Products and Services Code for categorization
• Custom Codes: Other codes as needed for identification or integration purposes

Services can be associated with forms that collect additional information from customers:

• Forms can be created and managed by suppliers
• Forms can include various field types (text, selection, etc.)
• Forms can be required for ordering certain services

Services can have pricing information associated with them:

• Prices can be set for different stores
• Prices can be in different currencies
• Prices may require approval from store operators
• Price lists can be created to manage pricing for multiple services

Services can be added to carts and ordered just like physical products:

• Services can appear in order logs and reports
• Services can be included in quotations

Services can be processed in batches for efficiency:

• Bulk import of services via CSV
• Batch updates to services
• Background processing of service-related tasks

The system enforces validation rules to ensure service data quality:

• Required fields must be provided
• Identifiers must be unique within a supplier's catalog
• URLs must be valid
• Properties must have string keys
• Service types must be valid (fixed or variable)