Marketplace ops
AuraScore 81/100

B2B Industrial Vendor Onboarding and Spec Compliance Architecture

Design a robust vendor ingestion and technical spec validation framework for industrial manufacturing marketplace suppliers.

Use this template when setting up or standardizing onboarding pipelines for complex manufacturing parts vendors. It establishes technical data validation, hazardous material documentation, and SLA compliance guardrails.

Template

Role: Principal Industrial Marketplace Architect with 15+ years in B2B heavy supply chain platforms.

Context

  • Target Marketplace System: {{marketplace_platform}}
  • Manufacturing Vertical: {{industrial_category}}
  • Regulatory & Technical Standards: {{compliance_standards}}
  • Ingestion Architecture: {{erp_integration_pattern}}
  • Target Supplier Segment: {{target_vendor_tier}}
  • Fulfillment Expectation: {{sla_lead_time_target}}

Task

Design an operational onboarding and technical compliance framework that systematizes industrial vendor qualification, catalog ingestion, and fulfillment validation on {{marketplace_platform}} without creating operational bottlenecks.

Method

  1. Map vendor lifecycle stages from initial credentialing to active transactional status for {{target_vendor_tier}}.
  2. Formulate catalog taxonomy and attribute ingestion gates, including dimensional drawings, material certifications, and {{compliance_standards}} metadata.
  3. Define real-time inventory feed requirements and automated price update logic via {{erp_integration_pattern}}.
  4. Design mandatory hazardous materials, storage class, and export control validation checkpoints for {{industrial_category}}.
  5. Establish operational sandbox test protocols to verify end-to-end order acknowledgments and ship-notification latency against {{sla_lead_time_target}}.
  6. Specify continuous monitoring mechanisms for supplier defect rates, catalog drift, and documentation expiry.
  7. Create tier-specific remediation playbooks for automated de-listing and probationary re-onboarding.

Constraints

  • Framework MUST mandate automated technical attribute validation before any product SKU goes live.
  • MUST NOT rely on manual document reviews for standard ERP feed synchronization.
  • Operational gates must explicitly support both make-to-stock and build-to-order industrial fulfillment modes.
  • All compliance failure points must trigger deterministic vendor notification webhooks within 60 seconds.

Output format

Return a structured operational framework with the following exact headers:

  1. Vendor Qualification & Technical Gate Matrix (table with Stage, Gatekeeper, Required Data, Pass/Fail Threshold)
  2. Catalog Normalization & Schema Protocol (attribute hierarchy and mandatory spec fields for {{industrial_category}})
  3. Integration Verification Architecture (pre-flight testing checklist across {{erp_integration_pattern}})
  4. Operational SLA & Compliance Governance Model (audit cadence, escalation triggers, and delisting protocol) Total response length must be between 1,200 and 1,800 words.

Self-review

  • Verify every context variable (including {{compliance_standards}} and {{erp_integration_pattern}}) is deeply integrated into the operational steps.
  • Ensure technical requirements are industrial-specific and not generic retail e-commerce guidelines.
  • Confirm all constraints, especially the automated gatekeeping rules, are enforced throughout the framework.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ecommerce-retail
ecom-operations
manufacturing-industrial
marketplace-ops
vendor-onboarding
industrial-b2b