Core Concepts

Before getting started, it's important to understand the core concepts that power Versable. These concepts form the foundation of every workflow in the platform and are referenced throughout the rest of this guide.

Modules

Modules are the four primary workflows in Versable:

• Data Extraction
• Validation
• Enhancement
• Image Generation

Each module can be used independently or combined into a larger workflow, depending on your needs.

Templates

Templates define how Versable understands input data and generates output data.

Upload Templates

Upload templates tell Versable how to read and interpret your input files. Because every supplier and system labels fields differently, upload templates map your file structure to Versable's internal data model.

Key points:

• Required for any input file including PIES, internal loadsheets, and supplier files
• Saved for reuse (e.g. “Supplier A Upload Template”)
• Prevents repeated manual mapping on every upload

Enhancement Templates

Enhancement templates define how content is generated in the Enhancement module.

They allow you to:

• Control formatting and structure
• Guide AI output instead of allowing free-form generation
• Save marketplace- or channel-specific formats

Enhancement templates are especially important when selling across multiple platforms with strict requirements.

Configuration

Some modules require one-time configuration before they can be used.

Website Configuration (Data Extraction only)

Before scraping a new website, Versable configures how that site should be accessed and parsed.

Key points:

• Each website requires its own configuration
• Configuration typically takes about one business day
• Once configured, the site can be reused indefinitely
• After configuration, extraction runs are fast and reliable

Rule Configuration (Validation only)

Rule configurations define the logic used by the Validation module.

Examples include:

• Mapping supplier part types to PCdb
• Mapping part types to an internal taxonomy
• Extracting structured values from application notes
• Formatting fitment data into ACES-compliant structures

To set up rule configurations:

• Schedule a short 15 minute support call with the Versable team
• Share your requirements
• Configurations are typically applied within a few days

Once configured, rules can be reused across files and workflows.

Credits

Versable operates on a credit-based system that gives you flexibility in how and when you use the platform, based on your workflow and usage needs.

Credits are allocated based on your plan and are consumed when you run modules such as data extraction, validation, enhancement, or image generation. This model allows you to prioritize high-impact work whether that's enriching a small set of SKUs or running large batch jobs without being locked into rigid usage patterns.

Because different workflows consume credits differently, the credit system makes it easy to balance experimentation, iteration, and production runs within your monthly limits.

To learn more about exactly how credits are consumed across modules, including real-world examples, refer to the Credit Consumption section later in this guide.

Now that you understand Versable's core concepts and capabilities, the next section will walk you through how to start using each module to power your product data workflows!