Solutions
Cutting-edge solutions tailored to everyday issues in the modern digital environment.
Services
Innovative tools and services designed to address complex challenges today’s digital landscape.
IT FOR What WE DO MENU
Services
Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.
IT FOR HOW WE DO MENU
Services
Hexagon is reshaping industries through smarter systems, streamlined workflows, and bold digital innovation.
Ready to clean up your CRM workflow?
Book a CRM Workflow Audit and see where leads, follow-ups, reporting, or disconnected tools can be fixed first.
Retail Channel Integration Platform
An integration that connects a health brand's Oracle ATG commerce platform to two big-box retail chains, each with its own data rules.
Business goals
The client built its business selling nutrition plans and packaged meals directly to consumers. Adding big-box retail meant its commerce system had to exchange data with two national chains. Each chain has its own item setup, formats and timing. The client needed those connections to work from its existing Oracle ATG platform, so the retail channel could grow without a parallel set of product and order records.
Project overview
Hexagon built the integration between the client's Oracle ATG platform and two big-box retail chains. Each chain got its own connection, with its own mapping rules, on top of shared integration logic. Product, price and order data moves between systems on a defined schedule. When a record fails, it stops in a queue with a clear reason, and staff can correct it instead of digging through log files.
Challenges faced and solved
Selling through a big-box chain means working to its data rules, while your own direct business keeps running.
Two chains, two sets of rules
Big-box retailers each dictate how items, prices and orders must be sent. A single generic feed will fail one of them, and a rejected item can mean a missed shelf date.
We gave each chain its own mapping layer on shared integration code, so a rule change at one retailer doesn't touch the other connection.
One product, many identifiers
The same meal kit carries an internal SKU, a retailer item number and a barcode. When those drift apart, orders land against the wrong item and someone has to untangle it by hand.
We built a cross-reference that ties each ATG catalog item to every chain's identifier, so all exchanged records resolve to one product.
Protecting the direct business
Direct-to-consumer orders pay the bills while the retail channel ramps up. An integration that slows checkout or changes the live catalog puts existing revenue at risk.
We ran retail data exchange as scheduled background jobs separate from shopper traffic, and kept channel-specific data apart from the consumer storefront.
Failures nobody notices
A silent feed failure often surfaces days later, when a buyer calls about a missing file or finance can't match an order. By then the fix is expensive.
We logged every exchange and sent failed records to a review queue with the reason attached, so staff can see problems the day they happen.
Features
| Feature | Description |
|---|---|
| Catalog and pricing | |
| 1. Retail Item Master | Each sellable item carries the attributes a chain requires, kept in Oracle ATG with the rest of the catalog. Merchandising staff work from one source. |
| 2. Identifier Cross-Reference | Internal SKUs are matched to each retailer's item number and barcode. Orders and reports then point to the right product. |
| 3. Per-Chain Catalog Feeds | Item data is formatted and sent to each chain to that chain's specification, so a format change stays contained. |
| 4. Channel Pricing | Retail prices are held apart from direct-to-consumer prices. A storefront promotion doesn't leak into a retailer's price file. |
| 5. Item Status Control | Staff mark items as active or discontinued by chain, because a kit may be sold at one retailer and not the other. |
| Orders and fulfilment | |
| 6. Inbound Order Import | Orders from each chain are received, checked and created as records on the commerce platform, without rekeying. |
| 7. Order Validation | Each incoming order is checked for known items, valid quantities and required fields before it moves on. |
| 8. Status Updates to Retailers | Order status goes back to the chain that placed the order, keeping both sides on the same page. |
| 9. Channel Tagging | Each order records which chain it came from, so retail volume can be separated from direct sales. |
| 10. Scheduled Exchange Jobs | Inbound and outbound runs follow a timetable set for each chain, outside the path shoppers use on the website. |
| Operations and support | |
| 11. Exception Queue | Failed records wait in one list with the reason shown. Staff fix and resubmit them without technical help. |
| 12. Exchange Log | Every file or message is recorded with time, chain and outcome, which answers the question of whether something was sent. |
| 13. Automatic Retry | Temporary connection failures are retried before anyone is alerted, which keeps the queue limited to real data problems. |
| 14. Failure Alerts | Staff are told when a scheduled run fails or doesn't arrive, so a missed exchange doesn't wait for a retailer's call. |
| 15. Reconciliation View | Sent and received records can be compared by chain and date, which gives finance and operations a place to check totals. |
How the platform is put together
Each layer has one job.
The result
The client's commerce platform can now exchange product and order data with both retail chains from one set of records.
| Area | Before | After |
|---|---|---|
| Retail connections | No link between the commerce platform and the chains | A dedicated connection for each chain on shared code |
| Item identifiers | SKUs and retailer item numbers kept in separate places | One cross-reference tied to the ATG catalog |
| Order handling | No automated route for retailer orders into the platform | Orders imported, validated and tagged by chain |
| Failed records | Problems hard to spot without technical help | A review queue with the reason shown |
How we took it from idea to launch
Good software follows a process. Here are the six stages, and what happens in each one.
Discovery & Requirements
Goal: Define the product vision, target audience and core business requirements.
Key activities- Stakeholder interviews
- Market and competitor research
- Defining user personas
- Drafting technical specifications or a Product Requirements Document (PRD)
Design (UX / UI)
Goal: Create an intuitive user experience and visual interface.
Key activities- UX design: information architecture, user flows and wireframes
- UI design: high-fidelity mockups and interactive prototypes in Figma or similar tools
- Design system: colors, typography and component libraries
Development: Frontend & Backend
Goal: Build the functional application using agile sprints.
Key activities- Backend: set up databases, design APIs (REST, GraphQL), implement server logic, and configure authentication and authorization (OAuth, RBAC)
- Frontend: build responsive interfaces and connect components to backend APIs
- Version control: manage code through Git and GitHub
Security & Optimization
Goal: Harden the application against vulnerabilities and boost performance.
Key activities- Security: address the OWASP Top 10, including injection, XSS and CSRF, enforce encryption in transit and at rest, and implement rate limiting
- Optimization: code splitting and lazy loading, database indexing, API caching and load testing
- QA and testing: unit, integration and end-to-end tests
Beta Release
Goal: Deploy to a controlled group of real users to catch edge-case bugs and gather feedback.
Key activities- Set up staging and production CI/CD pipelines
- Launch a closed or open beta with real users
- Monitor errors through observability tools
Public Release (Launch)
Goal: Roll the software out to the general public.
Key activities- Final production deployment
- DNS configuration
- Marketing and onboarding rollout
- Post-launch performance and security monitoring
Business benefits
The brand can reach big-box shoppers using the commerce platform it already runs.
One cross-reference reduces wrong-item errors between the brand and its retailers.
Orders no longer depend on someone retyping them between systems.
Shared integration code means a further retailer is a new mapping, not a new system.
Conclusion
Getting a product onto a big-box shelf is a commercial win. Keeping the data right afterward is daily work: items, prices, orders and status, all on the retailer's terms. Hexagon built this integration so the client's team could run that work from the Oracle ATG platform they already knew, with failures visible and fixable. If your brand is adding a retail channel, or your enterprise commerce platform needs to talk to a major trading partner, we'd be glad to talk it through.
Talk to us about your projectRelated services: API integration · custom software development
Related projects
FAQs
BUSINESS SYSTEMS
SOFTWARE
AI
INTEGRATIONS
Build, Improve, or Connect the Systems Your Business Depends On.
Whether you need custom software, CRM, ERP, AI, automation, integrations, or modernization, tell us what you’re trying to improve. We’ll review your requirements and recommend the most practical next step.
300+
Software projects delivered
37+
Enterprise apps built
150+
delivery team members
10+
countries served
Tell Us About Your Project
No sales pressure. Tell us what you’re trying to build, improve, integrate, automate, or replace. We’ll review your answers and come back with a clear recommendation within 1 business day.
Prefer to talk now? Call +1 (801) 259-4800 or book a free 30-minute consultation.
Custom software, CRM, ERP, AI, integrations, and business systems built to improve how growing organizations operate.
© 2026 Hexagon IT Solutions. All rights reserved.