1. Scenario: Product Data Coming From 4 Different Suppliers With Different Attribute Formats

Question:
You receive product data for the same SKU from four suppliers. Each supplier uses different attribute names, units, and formats. How do you ensure data standardization and survivorship in Stibo STEP?

Answer:
I start by creating a Global Data Model with standardized attributes. Then I use Mappings to map each supplier’s feed into STEP.
Next, I apply Business Rules for unit conversion, formatting, and mandatory-field validation.
For conflicting values, I configure Survivorship Rules (source priority, most recent update, or highest confidence).
Finally, I run the feed through STEP Workflows to validate, enrich, and approve the product before publishing.

What interviewer checks:
Understanding of mapping, workflows, survivorship, and data governance.

2. Scenario: SKU Must Not Go Live Without Images

Question:
Marketing insists that no product should be published to eCommerce unless images are present. How will you enforce this in STEP?

Answer:
I configure a Pre-Publish Validation Rule that checks image existence.
This rule is added as a mandatory task in the workflow.
If images are missing, the workflow routes the record back to Content Team for enrichment.
Only after images pass validation does the workflow allow publishing to downstream systems.

Strength:
Shows governance + workflow automation.

3. Scenario: Need to Manage Multiple Product Hierarchies

Question:
Your company wants to maintain separate hierarchies for eCommerce, Retail Stores, and Procurement. How will STEP support this?

Answer:
STEP allows multiple independent hierarchies.
I create separate hierarchies (eComm, Retail, Procurement) using Classification.
Entity objects (Products) are linked to all applicable hierarchies using multi-classification.
Business rules ensure each hierarchy receives correct attributes, images, and descriptions.

Hiring advantage:
Shows deep understanding of multi-domain strengths.

4. Scenario: Supplier Sends Incorrect GTINs Frequently

Question:
Suppliers often send wrong GTINs. How do you validate them automatically?

Answer:
I set up a GTIN Validation Rule using checksum logic in STEP.
When data is imported, the rule checks GTIN length, prefix, and checksum.
Invalid GTINs are moved to Error Queue for correction.
Suppliers get automated notifications via workflow tasks.

Impact:
Displays ability to reduce manual effort and improve data quality.

5. Scenario: You Are Migrating From Legacy PIM to Stibo STEP

Question:
During migration, legacy data is incomplete and inconsistent. What is your strategy?

Answer:

1. Profiling: Use data profiling to assess quality.

2. Standardization: Create a clean target data model in STEP.

3. Transformation: Apply rules for cleansing, deduplication, enrichment.

4. Loading: Load using Batch Integration Service (BIS) or APIs.

5. Validation: Run workflow-driven validation before go-live.

6. Governance: Enforce strong post-migration controls.

Strength:
Shows structured, leadership-level approach.

6. Scenario: Introduce a New Mandatory Attribute Mid-Year

Question:
A new regulatory attribute becomes mandatory. How do you update all existing products?

Answer:
I modify the Data Model to include the new attribute.
Then I run a Mass Update Workflow that identifies all records missing this attribute.
Data stewards enrich the data through workflow tasks.
Publishing is paused for non-compliant SKUs until the rule is satisfied.

Insight:
Demonstrates change management excellence.

7. Scenario: Two Records Represent the Same Product

Question:
How do you identify and merge duplicate product records?

Answer:
I create Match Rules based on GTIN, Manufacturer ID, and Brand.
STEP flags potential duplicates in the Duplicate Management Dashboard.
Data stewards review and run the Merge Operation which retains survivorship and crosswalk mappings.
This prevents duplicate publishing and ensures golden record consistency.

Competency:
Shows confidence with STEP’s deduplication engine.

8. Scenario: Send Product Data to SAP, Magento, and Data Warehouse

Question:
How do you design a scalable publishing model?

Answer:
I configure separate Outbound Templates for SAP IDoc, Magento CSV/API, and DW tables.
Workflows trigger publishing when a product reaches the “Approved” stage.
Using STEP Publish Engine, I schedule and monitor exports.
Error logs automatically route to data governance teams.

Leadership thinking:
Shows architecture-level awareness.

9. Scenario: Business Wants Faster New Product Onboarding

Question:
What will you optimize in STEP?

Answer:

• Simplify workflows

• Automate validations

• Add default values

• Pre-fill attribute sets based on category

• Introduce AI/Rules-based enrichment

• Reduce human approval steps where possible

Value:
Highlights productivity optimization.

10. Scenario: Audit Team Needs Change Tracking

Question:
How does STEP help with full audit history?

Answer:
STEP offers Versioning & Audit Trail out-of-the-box.
Every attribute change is logged with timestamp, user, and value differences.
I configure Audit Views and export logs for compliance reporting.

Strength:
Shows governance + compliance mastery.