← Real Cases
REAL CASEcase-rewi-micropos
Rewi + MicroPOS — promote the pattern, not the product
How two different products exposed reusable patterns without turning commercial particulars into global rules.
Context
Rewi and MicroPOS share several operational and integration problems while keeping different business models and boundaries.
Problem
There was a risk of copying a product-specific solution as if it were a universal Standard.
Evidence
- API/n8n integration comparison.
- Local persistence and deployment artifacts.
- Browser/QA and runtime-update evidence.
Decision
Promote only behaviors demonstrated as reusable patterns while keeping pricing, branding and commercial rules local.
What changed
Boundaries between Blueprint, Skill, Gate, project knowledge and reference evidence became clearer.
What we learned
- Common pattern ≠ common product.
- Gate Defect ≠ Product Defect.
- Business differences must survive standardization.
How to reuse it
- Commercial websites.
- Mini CRM patterns.
- Orchestrator integrations.
What NOT to generalize
- Commercial fields.
- Specific payment providers.
- Pricing.