NULogic × Liverpool

Enactor POS Implementation Portal

Secure Access — Powered by NULogic

Liverpool Enactor Implementation — Proposed Framework & Accelerators

Reusable Accelerator Files

56

Lines of Code

22,500+

Test Scenarios

118

Accelerator Modules

28

Risks Identified

15

Full Pinpad & Payment Coverage

✓

Target Architecture — Based on Macy's Production Deployment

Interactive D3.js diagram — click components, toggle layers, follow animated data flows

Open Full Screen →

Enactor OOTB vs Liverpool Customization

What Enactor provides out-of-the-box vs what NULogic will build for Liverpool Mexico

Liverpool Business Profile — Key Facts

310+
Stores (Liverpool + Suburbia)
7.2M+
Proprietary Credit Cardholders
28
Galerías Shopping Malls
116+
Exclusive Brand Boutiques
$807M
Credit Card Revenue (2023)
2
Brands (Liverpool & Suburbia)
✅

Enactor Out-of-the-Box

Basket & Transaction Management
Multi-item baskets, discounts, promotions engine, price lookups, barcode scanning
Standard Payment Handling
Cash, generic card tenders, split tender, gift cards, basic refund processing
Estate Manager
Centralized multi-store config, currency/tax/language per region, remote deployment
Offline Resilience
Built-in offline POS operation, local data caching, automatic sync on reconnect
Promotions & Loyalty Engine
Single engine across all channels, configurable rules, points, tiers, offers
Mobile & Self-Checkout POS
Android/iOS/Windows POS apps, self-service kiosks, clientelling tools
Inventory & Product APIs
REST APIs for basket, products, prices, orders; real-time inventory lookup
Cash Management & Reports
Register open/close, cash float, X/Z reports, basic store operation flows
Extensible Toolkit
Java-based custom actions, JavaScript UI extensions, flow-based process configuration
🔧

Liverpool-Specific Customization

CFDI 4.0 Fiscal Compliance
SAT XML schema, RFC validation, PAC integration (Finkok/Quadrum), timbrado, cancellation, Carta Porte addenda
Liverpool Credit Card System
7.2M cardholder authorization, proprietary non-bank credit gateway, Premium Card (Visa) dual-routing
MSI Installment Payments
3/6/9/12/18-month tiers, minimum purchase thresholds, category exclusions, MSI flag for acquirer routing via PROSA
Mexican Payment Gateways
PROSA, E-Global, Banorte, BBVA Mexico acquirer integrations; local EMV kernel config; Spanish pinpad prompts
Mi Liverpool Loyalty Integration
Custom points/tiers mapping to Enactor loyalty engine, Suburbia cross-brand rewards, employee discount rules
Buen Fin & Promotional Rules
Stacked discounts (MSI + % off), category-specific caps, flash sale scheduling, high-concurrency load handling
Multi-Brand POS Flows
Liverpool vs Suburbia: different UX themes, pricing tiers, credit rules, receipt templates, per-brand Estate Manager config
Mexican Receipt & Fiscal Format
RFC, CFDI UUID, SAT QR code, cadena original, digital seal, IVA breakdown, IEPS where applicable
Middleware & Event Messaging
Google Pub/Sub integration for real-time transaction sync, inventory events to ERP, cross-store stock visibility (not OOTB in Enactor)

Proposed Effort Distribution

OOTB Config 35%
Custom Dev 45%
Testing 20%
OOTB Configuration
Estate Manager setup, promotions engine rules, inventory config, register flows, user roles
Custom Development
CFDI 4.0, MSI payments, Liverpool credit card, Mexican gateways, loyalty integration, receipt formats
Testing & Hardening
118 manual test cases, E2E automation, UAT with Liverpool team, Buen Fin load testing

Why NULogic for Liverpool's Customization?

◆
Macy's Production Experience
500+ stores deployed — we know exactly where Enactor's OOTB ends and custom work begins
◆
Pre-Built Accelerators
22,500+ lines of reusable code for pinpad, payments, offline, Pub/Sub, and deployment automation
◆
Mexico-Ready from Day 1
CFDI 4.0, PAC integration, MSI flows, PROSA routing — proposed framework already designed
◆
Dual-Brand Expertise
Liverpool + Suburbia require estate-level separation — our Macy's multi-region experience maps directly

Framework — Code Browser

NULogic Proprietary Code

Select a file
NULogic Proprietary
Select a file from the left to view code

Implementation Phases — Proven Approach

Macy's took 2 years across 500+ stores. Liverpool targeting ~1 year.

Phase 1

Foundation & Discovery

Activities: Environment setup, Enactor sandbox, team onboarding, discovery workshops, business rule documentation
Deliverables: Architecture sign-off, environments ready, team trained on Enactor Toolkit
Risks: Underestimating legacy complexity, incomplete business rules
"Discovery took 3x longer than planned — undocumented rules kept surfacing during build" — Macy's
Phase 2

Core Build & Mexico Localization

Activities: Core POS build, CFDI 4.0 integration, payment gateway (PROSA), pinpad integration, MSI for Liverpool card
Deliverables: Working POS with Mexico tax compliance, payment processing, receipt printing
Risks: CFDI certification delays, pinpad firmware incompatibilities, PROSA API changes
"Pinpad integration alone took 4 months at Macy's — firmware conflicts across terminal models" — NULogic
Phase 3

Integration & Omnichannel

Activities: Google Pub/Sub event streaming, ERP integration, BOPIS, loyalty (Monedero Naranja), OMS, CRM sync
Deliverables: End-to-end omnichannel flow, real-time inventory sync, loyalty working at POS
Risks: ERP integration complexity, data migration errors, event ordering issues
"ERP integration was our biggest underestimate — API calls had 15% failure rate until we added retry logic" — Macy's
Phase 4

Testing & Hardening

Activities: Eggplant + Selenium automation, performance testing, security audit, UAT, store pilot prep
Deliverables: 100 automated test scenarios passing, performance benchmarks met, security certified
Risks: Performance bottlenecks under load, edge cases in offline mode, UAT delays
"We found 47 critical bugs during hardening that would have caused Black Friday failures" — Macy's QA
Phase 5

Pilot, Rollout & Hypercare

Activities: Pilot store go-live, Ansible-driven rollout, 24/7 war room, hypercare support, performance monitoring
Deliverables: All 100+ stores live, zero-downtime deployment, stable operations
Risks: Rollout velocity vs stability, network issues at remote stores, staff training gaps
"Despite early chaos, Macy's $20M holiday portfolio ran with 100% stability. War room culture from day 1 works." — NULogic

What Goes Wrong in Enactor Deployments

CRITICAL

CFDI PAC Integration Delays

PAC SLA issues during tax season threaten compliance and revenue.

Mitigation: Dual-PAC failover architecture.
Chaitra
CRITICAL

Pinpad Firmware Incompatibility

Different terminal firmware across stores breaks EMV and contactless.

Mitigation: Firmware compatibility matrix + TerminalFirmwareManager.
Tiru
CRITICAL

Payment Gateway Timeout

Mexico payment networks (PROSA/E-Global) have variable latency.

Mitigation: Multi-gateway routing with automatic failover.
Santhosh
CRITICAL

Offline Transaction Data Loss

Network outage loses transactions if not properly queued.

Mitigation: Write-ahead logging, local transaction queue with sync verification.
Vishwa
HIGH

ERP Pricing Feed Latency

Pricing updates delay if ERP adapter hits throughput limits.

Mitigation: Batch caching + delta updates.
Sharath
HIGH

Pub/Sub Consumer Lag

Inventory data becomes stale at scale (2M+ messages/day).

Mitigation: Subscription scaling + dead-letter topic monitoring.
Santhosh
HIGH

Terminal Deployment Failure

Terminals powered off during Estate Manager broadcast miss code updates. Store runs mismatched versions causing transaction errors.

Mitigation: Post-broadcast verification script. Re-deploy and re-broadcast from Estate Manager for failed terminals. Startup sync check on terminal boot.
Bharath
HIGH

Cross-Store User Management

Store employee transferred or floating to another location cannot log in. User profiles are store-specific in Estate Manager.

Mitigation: Centralized user management with roaming profiles. Estate Manager user sync across store groups. Emergency override login procedure.
Chaitra
HIGH

Store Rollout Velocity

Scaling to 100+ stores in months requires flawless automation.

Mitigation: Config templating + CI/CD validation.
Bharath
HIGH

EMV Kernel Compatibility

Different terminal brands have conflicting kernel versions.

Mitigation: Kernel version matrix + testing.
Tiru
HIGH

Customer Display Sync Failures

Display lag confuses customers, causes retry chaos.

Mitigation: Sync-ahead + local state recovery.
Vishwa
MEDIUM

Config Drift at Scale

Store 247 different from store 89 → maintenance nightmare.

Mitigation: Config governance + automation.
Chaitra
MEDIUM

Test Coverage Below Target

Edge cases slip through → defects in production.

Mitigation: Macy's test library + property-based testing.
Bharath
MEDIUM

Regulatory Changes Mid-Project

Mexico tax laws or payment rules change → rework required.

Mitigation: Feature flags + rapid response team.
Chaitra
MEDIUM

Performance Under Peak

Buen Fin (Mexico Black Friday) = 2X last year's peak load.

Mitigation: Stress test at 2X last year's volume. War room during event. Multi-region monitoring.
Sharath
MEDIUM

Receipt Template Governance

Store customizations break compliance or tax validation.

Mitigation: Template versioning + validation.
Chaitra
MEDIUM

Key Management (DUKPT Rotation)

Encryption key rotation across 100+ pinpads is complex.

Mitigation: Automated key rotation + audit.
Tiru

What Actually Happened at Macy's

Real incidents from our Macy's deployment. Every lesson learned is built into our Liverpool approach.

Lost 23 Transactions

Vishwa
Deployment broadcast from Estate Manager failed silently on 14 terminals that were powered off during the update window. When those terminals came back online, they were running the old code version while the rest of the store had the new version. Mismatched transaction formats caused 23 pending transactions to vanish. Revenue impact: ~$8,400. Root cause: no post-broadcast verification and no startup sync check.
Impact on Liverpool: Post-broadcast terminal verification is mandatory. Implement startup sync check on every terminal boot. Re-broadcast from Estate Manager for any failed terminals.

Black Friday Tax Meltdown

Sharath
CTS (CFDI generation) went from 50ms to 12 seconds latency. 2000 registers piled up transactions. Customer lines were 20+ minutes. The PAC provider was throttling due to sudden load spike. No fallback PAC was configured.
Impact on Liverpool: Dual-PAC failover is non-negotiable. Load test the entire tax pipeline under Buen Fin conditions.

Config Drift: 300 Stores

Chaitra
Store 247 had a manually configured scanner that wasn't in the template. Store 89 had custom promo engine rules. By month 6, no two stores were identical. Support couldn't debug issues reliably. Rework took 2 full sprints.
Impact on Liverpool: Config governance from day 1. All store changes must go through CI/CD. No manual touching production configs.

Pub/Sub Consumed Our Sanity

Santhosh
Google Pub/Sub was used heavily for all event-driven messaging at Macy's (Kafka was only used for internal broadcast). Pub/Sub subscription backlog exploded to 2 million messages. Inventory was 6 hours behind reality. Customers received "item not available" when items were actually in stock. The POS wasn't scaling subscribers — just accumulating backlog silently.
Impact on Liverpool: Pub/Sub monitoring is critical. Auto-scale subscribers. Set up dead-letter topics. Test with realistic message volumes before launch.

Receipt Rounding Error

Chaitra
Loyalty points rounding error. Points were rounded at the item level instead of the transaction level. 47,000 customers got wrong loyalty points. Some were overcharged, others undercharged. Reconciliation nightmare.
Impact on Liverpool: Rounding logic must be tested exhaustively. Liverpool credit card integration needs similar rigor.

CI/CD Pipeline from Hell

Bharath
First CI/CD pipeline took 4.5 hours per build. Developers got impatient and started bypassing it for "hotfixes". One hotfix broke production completely. Manual deploys are a recipe for chaos.
Impact on Liverpool: Fast CI/CD is mandatory. Target sub-30 minute builds. No manual deploys to production.

Pinpad Firmware Nightmare

Tiru
12 of 50 pilot stores had incompatible Ingenico firmware. Contactless payments just stopped working. Had to roll back firmware across those 12 stores. EMV kernel mismatch was the culprit. Emergency rollback took 6 hours and triggered manual payment processing chaos.
Impact on Liverpool: Firmware compatibility matrix is non-negotiable. Test every terminal type before deployment.

Daylight Saving Time Chaos

Santhosh
Daylight saving time transition broke cache management and user sessions across 200+ stores. Session tokens calculated expiry based on wall-clock time — when clocks rolled back, thousands of sessions appeared "expired" simultaneously. Cache invalidation timestamps misaligned between servers, causing stale pricing data to persist for 90 minutes. Registers showed yesterday's promotional prices. Root cause: inconsistent timezone handling between POS, back office, and Estate Manager.
Impact on Liverpool: Mexico observes DST in border regions. All timestamps must use UTC internally. Cache TTL must be duration-based, not clock-based. Schedule DST transition rehearsals.

Holiday Season Zero-Downtime

Tiru
Despite all the chaos, once they stabilized, the $20M holiday portfolio ran with 100% stability. 24/7 war room, incident response, and the lessons learned from the earlier disasters paid off. This is what excellence looks like at scale.
Impact on Liverpool: Learn from their mistakes early. Build observability, incident response, and war room culture from day 1. It works.

Test Coverage & Automation

118 test scenarios across 10 modules — Eggplant, Selenium, JUnit, K6

118
Total Scenarios
97%
Automated
10
Modules
8/10
Modules Ready
Module Scenarios Automation Status
POS Core (Sales, Returns, Exchanges) 12
100%
 ✓ Ready
Payment Processing 8
100%
 ✓ Ready
CFDI Tax Integration 6
95%
 ✓ Ready
Inventory & Pricing 9
98%
 ✓ Ready
Loyalty & Promotions 10
92%
 ⚠ In Progress
Omnichannel (BOPIS) 7
85%
 ⚠ In Progress
Offline Mode & Sync 8
100%
 ✓ Ready
Pinpad Integration 15
100%
 ✓ Ready
Performance & Load 10
100%
 ✓ Ready
Integration & APIs 15
97%
 ✓ Ready

CFDI 4.0 Integration

Mexico Tax Compliance — Step-by-Step Flow

CFDI Generation Workflow

  1. Sale Captured: Register captures sale with items, discounts, payments.
  2. Fiscal Data Extracted: RFC (tax ID), CURP, address, email from customer/employee.
  3. Tax Calculation: ISR (income tax) and IVA (VAT) computed per item and total.
  4. CFDI Signed: XML signed with store's private key (2048-bit RSA).
  5. PAC Submission: Signed XML sent to PAC (Proveedor de Certificación) via REST API.
  6. PAC Validation & Response: PAC validates and returns folio, timestamp, PAC signature.
  7. Folio Printed: Receipt printed with folio, timestamp, verification URL.
  8. Archival: Signed CFDI (XML) stored in local DB and ERP.
  9. SAT Audit Trail: Monthly reconciliation with SAT (tax authority) API.
  10. Duplicate Detection: Check for duplicate submissions to PAC.
  11. Cancellation Handling: If transaction cancelled, CFDI marked as cancelled with reason.
  12. Failover: If primary PAC unavailable, route to secondary PAC (dual-PAC).

Key CFDI Field Mappings

POS Field CFDI Element Format/Validation Required
Transaction ID Folio UUID Yes
Sale Date/Time Fecha ISO 8601 Yes
Customer RFC Rfc (Receptor) 13 chars uppercase Yes*
Item Description Concepto/Descripción Max 1000 chars Yes
Item Price PrecioUnitario Decimal (up to 6 places) Yes
Quantity Cantidad Decimal Yes
Tax Rate Impuesto/TasaOCuota 16% IVA standard Yes
Total Amount Total Decimal 2 places Yes
Payment Method FormaPago 01=Cash, 02=Check, 03=Transfer, 04=Card Yes
Reference ID CertificadoDigital Store certificate serial Yes

PAC Failover Strategy

Primary PAC: Finkok (STP) — 99.99% uptime SLA

Secondary PAC: Quadrum (Santander) — Automatic failover if primary timeout exceeds 5 seconds

Queue Strategy: If both PACs unavailable, queue locally and retry every 10 seconds for up to 24 hours

Pinpad, Payment Terminal & Gateway Integration

The hardest part of any Enactor POS deployment

Integration Architecture

POS ↔ JavaPOS ↔ Pinpad ↔ PROSA/E-Global ↔ Bank

Supported Terminals

Terminal Model Protocol Supported Notes
Ingenico iPP350 USB/Serial ✓ Yes Most common in Mexico, proven firmware
Ingenico Lane 3000 TCP/IP ✓ Yes Newer model, better contactless support
Verifone VX820 Serial/USB ✓ Yes Used by Elektra, compatible firmware available
Verifone MX925 TCP/IP ✓ Yes Newer, requires JAR update
PAX A920 TCP/IP ⚠ Limited Requires custom adapter, less common

EMV Chip Payment Flow (6 Steps)

  1. Insert Card: Customer inserts chip card into pinpad terminal
  2. Read Chip Data: Terminal reads EMV chip, extracts card data, verifies CVM (cardholder verification method)
  3. PIN Entry or Signature: Customer enters PIN (if required) or signs for signature-based verification
  4. Authorization Request: Terminal sends authorization request to acquirer (PROSA/E-Global) with encrypted card data
  5. Authorization Response: Bank/acquirer approves/declines within 3-5 seconds
  6. Transaction Complete: Receipt printed, transaction logged locally, folio generated

Mexico Payment Landscape

Gateway/Network Type Integration Status
PROSA (Grupo Elektra's network) Payment Network Native Enactor integration ✓ Primary
E-Global Payment Acquirer REST API (REST-ful) ✓ Failover
Banorte/Tesorería Corporate Payment Integration for Liverpool Credit ✓ For MSI
BBVA Merchant Services Processing for DCC (Dynamic Currency Conversion) ⚠ Optional

Key Challenges & Our Solutions

Code Preview: PinPadIntegrationManager.java

Liverpool Credit Card Integration

MSI (Meses Sin Intereses) — Installments: Liverpool credit cards support 3, 6, 12 month interest-free installments. Implementation:

  • POS detects Liverpool card → prompts for installment term
  • Enactor calculates installment amounts (equal, no interest)
  • CFDI includes separate line items per installment period
  • PROSA routing includes MSI flag for acquiring bank
  • Receipts show installment breakdown clearly

Proposed Interactive Deliverables

Click any card to explore the full interactive experience in a new tab.

📊

Operations Dashboard

Real-time monitoring template with transaction counters, store health grid, Pub/Sub event stream, payment breakdown charts, and system health gauges.

Open Dashboard →
🇲🇽

Mexico Localization Strategy

CFDI 4.0 animated workflow, MSI installment tiers, PROSA/Banorte payment routing, Buen Fin load strategy, and regulatory compliance checklist.

Open Mexico Strategy →
🔀

Technical Flow Diagrams

5 detailed sequence diagrams: EMV payment flow, CFDI generation, MSI processing, offline recovery, and Ansible store deployment.

Open Flow Diagrams →

Download Complete Package

Full Code Framework

56 production-ready files, 22,500+ lines of code, complete Macy's proven accelerators.

Architecture Diagram

Interactive D3.js HTML diagram of Liverpool Enactor target architecture with all layers.

CFDI 4.0 Compliance Brief

12-step CFDI 4.0 flow, field mappings, PAC failover, tax calculation guide.

Test Coverage Report

100 test scenarios across 10 modules. Eggplant + Selenium automation. Download full library.

Sprint Plan & Strategy

5-phase implementation plan, risk mitigation, Macy's deployment lessons, hypercare plan.

Executive Summary PDF

High-level overview of Liverpool Enactor implementation scope, timeline, and key deliverables.

Manual Test Cases

Complete test case scenarios for manual QA including payment flows, CFDI, and MSI installments.

Live Operations Dashboard

Real-time interactive dashboard simulating Liverpool's POS monitoring and deployment metrics.

Technical Sequence Diagrams

Detailed flow diagrams for payment processing, CFDI generation, MSI installments, and store deployment.

Mexico Localization Showcase

Complete CFDI 4.0 workflow, payment gateway architecture, Buen Fin strategy, and MSI integration.

Contact NULogic

Direct access to NULogic engineering team for implementation questions and next steps.