Sold?out items in catalog emails to Adobe Commerce–SFMC pre?send validator and swaps

Overview

A specialty retailer’s Marketing & Customer Engagement team kept sending catalog emails that featured products already out of stock by the time customers clicked through. Intelligex integrated real-time inventory from Adobe Commerce (formerly Magento) into their email service provider and added a pre-send validator that automatically removed unavailable stock keeping units (SKUs) or suggested safe substitutions. Without changing the retailer’s campaign calendar or templates, send prep became calmer, customer disappointment eased, and the team stopped scrambling for last-minute edits.

Client Profile

• Industry: Specialty retail, direct-to-consumer eCommerce
• Company size: Mid-market, nationwide footprint
• Stage: Established omnichannel retailer modernizing marketing operations
• Department owner: Marketing & Customer Engagement
• Other stakeholders: eCommerce, Merchandising, IT, Customer Service

The Challenge

The team curated weekly catalog-style emails and automated journeys tied to seasonal drops. Inventory moved quickly due to limited runs and vendor allocations. Their email platform populated product blocks from a nightly file feed exported from Adobe Commerce. When a campaign deployed mid-day, that feed could already be stale. Customers clicked into “featured” items that had just sold through. The marketing team then fielded apologies on social channels, edited content on the fly, and sent follow-up messages—none of which helped customer trust.

Content production became a chain of workarounds. Designers built modules with manually pasted SKUs, marketing ops refreshed feeds and rechecked links in staging, and merchandising answered frantic pings about last-known quantities. The team considered switching platforms but could not pause campaigns or rebuild the stack. They needed a way to keep using their existing email platform and templates while enforcing a simple rule: do not promote what cannot be bought.

Budget and time were tight. IT was already committed to site performance, checkout enhancements, and vendor integrations. The solution had to be additive, stable, and governed, with minimal risk to campaign deadlines and no complex retraining of the entire marketing org.

Why It Was Happening

Inventory truth lived in Adobe Commerce, but the email platform pulled data in batches. The two systems spoke on a lag, and no control in the send workflow verified availability at the moment of deployment. Even when last-minute checks happened, proof emails did not simulate real-time stock, so the team was confirming content against stale snapshots.

Operationally, ownership was split. eCommerce owned product data, Marketing owned templates, and Merchandising owned what to feature. Each team made rational decisions within its tools, but there was no shared gate to reconcile SKU status across systems before messages left the door. Templates lacked fallback logic for substitutions, and governance relied on manual diligence rather than automated validation.

The Solution

Intelligex built a lightweight inventory service that sits between Adobe Commerce and the email platform, exposing real-time availability to templates and enforcing pre-send validation. We integrated with Adobe Commerce’s Web API to check SKU status at send time and inserted a validator into the existing email workflow. The validator removed unavailable SKUs and, when configured, swapped in safe alternatives from the same category based on merchandising rules. Marketing retained control with a human-in-the-loop approval step for any changes. No templates were rebuilt; modules now fetch inventory-aware content via a governed API call.

• Integration to Adobe Commerce inventory via REST, using documented endpoints: Adobe Commerce REST API.
• Email platform integration with Salesforce Marketing Cloud (SFMC) via content blocks and server-side scripts, aligned to SFMC APIs.
• Pre-send validator service that scans all SKUs in a campaign or journey and flags, removes, or substitutes items based on configurable rules.
• Template-safe helper that evaluates each product block at render time, hiding modules that resolve to unavailable SKUs.
• Fallback logic for category-based substitutions, honoring merchandising exclusions and margin thresholds.
• Short time-to-live (TTL) caching to minimize load on Adobe Commerce while keeping answers fresh.
• Human-in-the-loop review gate in the campaign checklist that surfaces changes and requires sign-off for substitutions.
• Logging, dashboards, and an audit trail for each send, including what changed and why.
• Permissions model that lets marketing ops override suggestions, with automatic recording of rationale.
• Health checks, rate limiting, and graceful degradation if the upstream API is slow or unavailable.

Implementation

• Discovery: Mapped the highest-risk templates and journeys where availability mattered most, identified how SKUs were referenced, and documented the current export schedule and latency. Aligned definitions of “in stock” across eCommerce and Merchandising.
• Design: Defined the API contract for SKU lookups and response payloads. Designed substitution rules with Merchandising, including category constraints and restricted brands. Specified validation outcomes: block, hide, substitute, or approve as-is.
• Build: Implemented a stateless service that queries Adobe Commerce for SKU availability and exposes endpoints the email platform can call. Created SFMC-compatible helpers to fetch inventory states during email render and a pre-send validator that scans a campaign’s manifest.
• Testing and QA: Ran the validator in shadow mode, scanning live campaigns without making changes, and compared outcomes to post-send site data. Simulated stockouts, variant unavailability, and partial catalog gaps. Verified audit logs and error handling.
• Rollout: Enabled the pre-send gate for a small set of catalog emails, then expanded to key journeys. Substitutions started in suggest-only mode; automatic removal of unavailable modules came later. Feature flags allowed instant revert if needed.
• Training and hand-off: Created a concise playbook for marketers: how to run validation, interpret flags, approve substitutions, and override when required. Set up a support channel with IT for escalations and a weekly review with Merchandising for rule tuning.
• Human-in-the-loop review: All substitutions and removals appeared in a pre-send checklist. Marketing approved or adjusted before finalizing, with every decision captured in the audit trail.

Results

Send preparation stopped revolving around emergency edits. The validator found issues early, removed or replaced risky SKUs, and presented a clean, reviewed slate for final proofs. Campaign managers no longer cycled between spreadsheets, product pages, and chat threads to confirm availability. The team reclaimed time to focus on creative, segmentation, and offers, not firefighting.

Customer disappointment eased. Clicks aligned with actual inventory, and service teams saw fewer contacts about missing items. Merchandising gained confidence that promotional priorities would be honored without accidental promotion of unavailable products. Compliance and brand risk dropped as product claims in email matched site reality. Overall, the marketing and eCommerce partnership strengthened thanks to shared visibility and a common gate before sends.

What Changed for the Team

• Before: Manual checks against nightly feeds; After: Automated, pre-send validation against live inventory.
• Before: Last-minute content surgery; After: Rule-driven removal or substitution with clear approvals.
• Before: Ambiguity about what “in stock” meant across systems; After: Single definition enforced in templates and workflows.
• Before: Constant pings to Merchandising for availability confirmation; After: Self-serve visibility with an audit trail.
• Before: Risky reliance on proof emails; After: Validator gate that mirrors send-time conditions.
• Before: Multiple spreadsheets and ad hoc scripts; After: Integrated service within existing platforms.

Key Takeaways

• Validate availability at the moment of send; batch feeds alone cannot protect customer experience.
• Integrate with existing platforms rather than rebuilding templates; small, well-placed services drive outsized operational gains.
• Use shadow mode first to build trust in automated checks before enforcing changes.
• Define a shared, enforceable meaning of “in stock” and codify it in rules both Marketing and eCommerce accept.
• Design fallbacks and substitutions upfront; hiding risky content is better than promoting what cannot be purchased.
• Keep humans in the loop for visible changes, with a tight audit trail to support governance and learning.

FAQ

What tools did this integrate with?
Adobe Commerce (formerly Magento) for real-time inventory via REST APIs, and Salesforce Marketing Cloud for email assembly and send orchestration. The service can also reference a product information management system if present, but that was optional for this retailer.

How did you handle quality control and governance?
A pre-send validator scanned every campaign and journey for risky SKUs, applied rules, and produced an approval report. Marketing reviewed and approved substitutions or removals before sending. All changes were logged with the who, what, and why, and dashboards showed patterns over time so Merchandising could refine rules. Changes to validation rules followed the same change-control process as other marketing assets.

How did you roll this out without disruption?
We ran the validator in shadow mode to prove accuracy without touching live campaigns. The first enforcement step only removed clearly unavailable items; substitutions launched in suggest-only mode. Feature flags allowed instant rollback, and we started with a small set of templates before expanding. Training focused on a simple checklist inside the existing workflow.

What happens if the inventory API is slow or unavailable?
The service uses timeouts, short TTL caching, and graceful degradation. If live checks cannot complete, templates fall back to the last verified snapshot or hide modules that cannot be confirmed. The validator blocks only high-risk content in that state, and the audit log records the behavior so the team can follow up post-send.

Does this handle variants and store-level inventory?
Yes. The rules can evaluate variant-level availability such as size or color and respect merchandising preferences. The initial scope focused on eCommerce fulfillment sources to keep decisions consistent; store-level logic can be layered in for campaigns that call for local pickup or regional targeting.