Integration
Stibo STEP workflow and import readiness
STEP onboarding is a workflow-state problem as much as it is an import problem. Supplier data has to satisfy mandatory attributes, mandatory references, and business-rule checks for the specific state and transition it is entering.
That is why the useful page is about state readiness, transition readiness, and STEPXML structure. It should help catalog operators understand what blocks movement through STEP, not just promise that a supplier file can be mapped somewhere.
What teams are really solving here
The real launch question for STEP is whether a product can move safely through the next workflow transition with its mandatory attributes, references, and business rules intact.
Teams can map the right values and still fail the workflow because the target state requires attributes that were never populated in the source.
STEP references are often the hidden blocker. A product looks complete until a mandatory brand, category, or related-object reference is missing.
Business rules create failures that feel opaque to suppliers because the file looks structurally sound but violates a transition rule inside STEP.
STEPXML imports can fail for structural reasons long before product content quality is even evaluated.
Supported inputs, with destination-specific handling
These are the source types we actively turn into Stibo Systems STEPworkflows. Each one has a different failure profile, so the useful part is how the data gets normalized before it reaches the destination.
STEPXML exports
Source pathSupplier reality
STEPXML exports preserve structure and references, but even small template deviations can make the import unusable.
What Rastro does
Rastro validates template structure first, then maps the payload into the target workflow context so state-level requirements are checked before import.
Destination constraint
STEPXML is only valuable if it matches the expected template and preserves the references needed for the next workflow transition.
Excel spreadsheets
Source pathSupplier reality
Spreadsheet onboarding usually captures attributes but misses workflow state, references, and object relationships.
What Rastro does
Rastro maps spreadsheet columns into STEP attributes, infers workflow context, and calls out missing references before the record enters STEP.
Destination constraint
A well-formed spreadsheet still fails if the destination state expects references or business-rule coverage the file cannot express directly.
PDF spec sheets
Source pathSupplier reality
PDF catalogs are useful for attribute recovery but weak for relationship and workflow-state information.
What Rastro does
Rastro extracts product facts, structures them, and identifies which state-level requirements still need reference or rule data from another system.
Destination constraint
Unstructured sources can help fill attributes, but they do not replace the mandatory references and workflow context that STEP enforces.
Manufacturer URLs
Source pathSupplier reality
Manufacturer sites can fill descriptive and technical gaps but rarely expose the object relationships STEP workflows depend on.
What Rastro does
Rastro scrapes structured facts and assets from the source page, then isolates the reference and workflow-state data that still has to be provided internally.
Destination constraint
Destination readiness is determined by workflow transition logic, not by whether rich product content was available on the web.
Supplier portal exports
Source pathSupplier reality
Supplier portals often capture submission forms, attachments, and attribute values, but not the internal STEP transition requirements.
What Rastro does
Rastro treats the portal export as one input into a larger readiness check that covers mandatory references and business rules before the STEP handoff.
Destination constraint
Portal completeness is not the same as workflow readiness. The record still has to satisfy the exact state and transition criteria configured in STEP.
Workflow stages that matter
We do not treat these destinations as generic import targets. Each stage below reflects the point where products usually stall for this specific platform.
Admit STEPXML, spreadsheets, PDFs, URLs, and portal exports, but start by checking whether the chosen import path can support the destination state and workflow design.
Map source fields to STEP attributes and object types while also identifying which values are attributes versus which must be expressed as references or workflow metadata.
Evaluate state readiness and transition safety before import so the record does not get stuck between workflow states after the technical load succeeds.
Run business-rule validation and mandatory-reference checks against the exact transition path the product is supposed to take inside STEP.
Only treat data as publishable once the workflow can advance cleanly, the required references exist, and the content survives the target state checks.
What a first passing batch looks like
These are the signals we expect before calling a handoff safe enough to launch. They are meant to reflect what good operational output looks like on this destination, not a generic import success message.
The product has the mandatory attributes needed for the exact workflow state it is entering, not just a generally complete attribute set.
Required references are in place so the next workflow transition can happen without a hidden stall in STEP.
Business rules have been checked before import, which means the record can move through governance instead of failing after load.
If STEPXML is used, the template is structurally valid before content quality becomes the next question.
Failure taxonomy we use on this destination
These are the recurring blocker patterns we classify before data is handed off. They map to the exact operational problems teams spend time fixing in Stibo STEP.
Workflow state mandatory attribute missing
The destination STEP workflow state requires attributes that are still empty, so the product cannot safely enter or progress through that state.
Workflow transition reference missing
One or more mandatory references needed for the next workflow transition are missing, so the record stalls even when its attribute values look complete.
Business rule failed
A STEP business rule prevents the record from advancing. This usually means the source data violates a transition, quality, or workflow condition configured inside STEP.
STEPXML template invalid
The STEPXML structure itself does not match the expected template, so the import fails before the destination can even evaluate product content quality.
Workflow transition not safe
The current payload may load, but it is still risky to move through the intended STEP workflow because readiness conditions for the next transition are not fully met.
Breakpoints we diagnose before data hits Stibo STEP
These are the concrete breakpoints that usually stop import, workflow progression, or publication. The point is to surface the exact thing that needs fixing, not to hand-wave about readiness.
Transition Blocker Finder
Returns the exact missing attributes and references that block the next STEP transition for a specific state.
Open toolMandatory Attribute Triage
Shows which state-level mandatory attributes are empty even when the row looks broadly complete.
Open toolMandatory Reference Triage
Flags the missing references that usually only show up when STEP refuses the transition.
Open toolPublic tools are live for the sharpest failures
We publish self-serve tools only when they are useful on their own. Broader or more customer-specific diagnostics for Stibo Systems STEPstill run as part of assisted onboarding when the failure mode depends on private schemas, workflow config, or recipient rules.
Send a supplier file to run these checksOperator FAQ
The questions below are the practical ones catalog teams usually ask before they put a real supplier batch through this destination.
Why is STEP onboarding so often a workflow problem instead of an import problem?
Because STEP usually enforces governance through states, transitions, references, and business rules. A file can import and still be unusable if it cannot enter or progress through the intended workflow.
What matters more in STEP, attributes or references?
Both matter, but references are often the hidden blocker. Teams usually notice empty attributes first, while the real reason a record stalls is a missing mandatory reference needed for the next transition.
What makes STEPXML a separate readiness problem?
STEPXML has its own structural expectations. If the template is wrong, the file never reaches the stage where workflow rules or product completeness can even be evaluated.
What should Rastro prove before a STEP handoff is called safe?
That the payload can enter the intended state, satisfy mandatory attributes and references, pass business rules, and avoid getting stranded at the next transition.
Stibo Systems attribute type coverage
All 11 attribute types supported, including localizable and scopable variants
Stibo Systems attribute type coverage
All 11 attribute types supported, including localizable and scopable variants
TextNumberIntegerDateListOfValuesBooleanUnitAssetReferenceProductReferenceDataContainerMultivaluedSee it on your own catalog
We'll deploy a demo portal with your PIM schema and map one real supplier file so you can see the output.