From Pharmacy to Marketplace
KogniVera x KIBO Partnership
Introduction
A large Mexican pharma retail giant stood as Mexico’s leading pharmacy retailer with thousands of physical stores and a growing online presence. The company had built its reputation on trust and convenience. But the retail landscape was shifting. E-commerce adoption across Latin America was accelerating, and customers wanted more product variety than any single retailer could stock.
Challenges Faced
The operational complexity behind a single customer order proved daunting. This retailer had spent years perfecting their first-party commerce operations. They owned the inventory, managed the warehouses, and controlled the delivery process. Everything was linear and predictable. But a marketplace model would change everything. A single customer order could include items from multiple sellers, each with its own warehouses, delivery partners, and service level agreements.
Key Obstacles
• Payment orchestration became complex. The retailer collected payment from the customer and then needed to distribute the payments to each seller after deducting commissions.
• Returns became a nightmare. Returns had to go back to the specific seller who fulfilled the order. Traditional systems had no concept of seller-specific return routing.
• Hardcoded rules could not scale. Every new seller requires a new rule configuration or code changes.
• Static routing could not handle real-time conditions. A seller might have inventory at 9 AM but sell out by 10 AM. Systems relied on last night’s batch feed.
The marketplace needed to launch within months, not years. They needed an order management system built to handle multiple inventory owners, delivery partners, and dynamic decision-making. KogniVera helped with that.
Solution
The large Mexican pharma retail giant engaged KogniVera as their implementation partner. KogniVera recommended KIBO OMS as the foundation for their marketplace fulfillment orchestration. KIBO OMS offered native support for distributed fulfillment and was built to handle thousands of sellers from day one.
Single source of truth
The team established KIBO OMS as the primary source of truth for orders. Every order entered KIBO OMS at creation, and every status change was recorded there. Other systems could update KIBO OMS via APIs, but KIBO OMS never delegated its authority.
Benefits delivered:
• Customer service had one place to check order status.
• Accurate Estimated Delivery Dates (EDD)
• Real-time shipment tracking
• Consistent order status visibility
• Unified order history
Intelligent order splitting and dynamic routing
The system evaluated multiple factors in real time when routing orders:
• Fulfillment availability
• Seller and location eligibility
• Estimated delivery dates
• 3PL capabilities
• Shipping constraints
• Business rules
No single carrier was optimal for all scenarios. A local courier might be faster and cheaper for same-city deliveries, while a national carrier might be better for cross-country shipments. KIBO OMS automatically selected the optimal provider for each shipment.
Bidirectional returns synchronization
Returns could originate in either the marketplace or the seller system and stay synchronized. When a customer initiated a return, KIBO OMS validated the order, determined which seller should receive the return, and coordinated the entire process. This prevented the common problem where returns get out of sync between systems, leaving customers confused.
Supporting sellers with multiple warehouse locations
When a seller had multiple warehouses, KIBO OMS treated each as a distinct fulfillment location. The engine evaluated each independently based on inventory and delivery promise. This allowed sellers to keep fast-moving inventory in multiple cities while reducing shipping costs and delivery times. New warehouse locations could be added with no code changes.
Using KIBO OMS extensions
Extensions allowed custom business logic to be inserted into KIBO workflows without modifying the core platform. This saved significant development time and protected the ability to upgrade the platform in the future.
Key Business Results
The complete marketplace fulfillment orchestration solution was delivered in just four months. The marketplace launched on schedule with full production capabilities.
Seamless customer experience
Customers could buy from multiple sellers in a single cart while seeing one unified order status. Behind the scenes, KIBO OMS managed the complexity. Sellers were paid accurately. Deliveries met service level agreements.
Business growth unlocked
• Product assortment expanded without purchasing more inventory.
• Third-party sellers gained access to an established customer base.
• New revenue streams were created.
• Competitive position strengthened
Cost and time savings
Intelligent order routing reduced shipping costs and delivery times. A customer in Guadalajara ordering from a seller with warehouses in both Guadalajara and Mexico City received faster delivery at a lower cost through automatic warehouse selection.
Key results at a glance:
• Complete solution delivered in just 4 months
• Thousands of sellers are managed through a single platform.
• Real-time order routing across multiple 3PL providers.
• Bidirectional returns synchronization is fully operational.
• Seller settlements automated with accurate commission calculations.
• Product assortment expanded without additional inventory investment.
Lessons learned:
• Start with a marketplace-ready OMS to reduce custom development.
• Use configurable routing rather than hardcoded rules.
• Integrate multiple 3PLs from day one.
• Prioritize bidirectional returns synchronization.
• Involve real sellers in testing before launch.
The large Mexican pharma retail giant now operates a production marketplace serving customers across Mexico. They proved that the operational complexity behind a single customer order can be managed efficiently and at scale with the right order management system architecture.