Skip to content

James Allman | JA Technology Solutions LLC

ENCOR (ISS45) Enhanced Promotions: A Field Guide for Grocery and Retail Technology Leaders

What the platform supports, the promotional patterns it makes possible, and how to bring more of them to life across your fleet.

ENCOR is a point-of-sale platform deployed across mid-size grocery and specialty retail in North America, in continuous production at hundreds of chains for two decades and longer. Inside that platform sits a capable promotion engine — Enhanced Promotions, Group Promotions, and Order/Level Promotions.

It drives loyalty, delivers supplier-funded bundles, runs tiered quantity rewards, targets by customer segment, and executes a wide range of promotional patterns. For chains running Enhanced Promotions — most ENCOR chains have the module in place — these capabilities are available today across the fleet, ready to put to work.

The sections that follow walk through what the engine can do, the day-to-day promotional patterns it supports, and how JA Technology Solutions helps chains bring more of that capability live — quickly, cleanly, and with the deep platform knowledge to deliver each promotion correctly across every store, every week.

ENCOR in plain language

Same platform under successive owners; ISS45 is still the field name for what is now branded ENCOR.

For readers who may not know the technical lineage: ENCOR is the modern brand name for the platform historically known as ISS45, a name still widely used in the field. The platform grew through most of its commercial life under Retalix until NCR's acquisition of Retalix in 2013. Today the platform is branded ENCOR. Hundreds of mid-size grocery, convenience, and specialty retail chains across North America rely on it.

The platform architecture that delivers it

Every promotion and item file change flows through this pipeline on its way to the register.

The architecture has been the backbone of ENCOR's longevity. POSWare is the application layer, sitting on every back-office server in the chain. SQL Server is the relational source of truth. QDX is the proprietary store-level data file format the lanes consume. Integration happens through ASCII batch files dropped into the Office Import directory, where BatchExe.exe polls the directory roughly every thirty seconds and ingests each file in turn. PosMaintAcx.exe propagates SQL changes out to the QDX files on the lanes. PCMCRC verifies and rebuilds QDX against SQL whenever the two need to be brought back into alignment.

That pipeline — host to import directory, BatchExe to SQL, PosMaintAcx to QDX, QDX to lane — is where every promotion, item file change, department, loyalty program, and linked-item rule actually lives. Working with ENCOR at depth means working with this pipeline at depth: knowing how each batch family flows through it, which records land where, and how to deliver every promotion cleanly to every store on schedule.

I started working with the platform in its earliest US deployments — alongside the original engineering team that built it — and have carried that depth forward through every platform generation since.

What the promotion engine can do

Three promotion types, each with a different structural reach.

Three promotion types form the engine. Enhanced Promotions handle single-group structures: a flat reward triggered by purchase from one defined group. Group Promotions extend that to as many as ten groups, each with its own quantity, value, or weight threshold. Order/Level Promotions support up to five reward tiers triggered at increasing thresholds — the structure that makes tiered quantity discounts and escalating-reward campaigns possible.

The reward catalog is broad. Cash off, percentage off, BOGO at the lower or higher matched price, free items, new flat prices, points and credits posted to the loyalty card, member-account rewards, target messages, multi-reward target messages, structured promotion deals, and tier-based new prices that change as the basket grows. Each reward type plays differently across funding models, conflict resolution, and reporting.

Group typing controls how the trigger evaluates basket contents. Promotions can operate on units, on weighted decimal items (meat, deli, produce), on accumulated value, on credits earned, or against the order total. Selecting the right group type for each campaign is a craft skill that rewards experience with the engine — and the right type makes the rest of the configuration straightforward.

Time and day windows operate independently per day of week, with separate start and end times for each day. Up to sixteen customer segments can gate eligibility, and as many as ten member card schemes can be linked to a single promotion. Coupon flow integrates as none, one-time, or one-time-per-reward. Funding is retailer, supplier-funded through several mechanisms, or split. Conflict resolution rules govern what happens when multiple promotions match the same line. Linked promotions bind to PLU, Department, Mix & Match, Manufacturer, Price Group, or Segment scope.

Each of these capabilities is available today on every back-office server in the chain, ready to be configured and deployed.

Multi-unit and quantity-tier offers

Reward escalates with quantity — the structure that drives stock-up basket size.

Buy three, get the fourth free, with a cap. Customer purchases three of an item and receives the fourth free, capped at a maximum number of free items per transaction; member-card-required, available across all card schemes. Drives multi-unit basket size on staple items while keeping the offer's exposure bounded. The cap and card-scheme link reward careful batch design — well-set, the offer behaves identically at every register every time.

Buy N for a new price with a minimum purchase threshold. Customer buying a specified quantity gets a flat new per-unit price, conditional on a minimum spend across the basket. Drives volume on price-sensitive items while protecting a margin floor. The interaction between the quantity threshold and the per-transaction limit handling is where deep platform knowledge pays off — the configuration that holds up at peak hours is the one built with both thresholds intentionally in mind.

Cents off per item after the second item. Standard price on items one and two, automatic cents off on items three through a defined cap. Encourages stock-up behavior while preserving the first-purchase price point. The dual-threshold structure is what makes the offer work at the margin, and getting both thresholds set correctly is straightforward when the configurator knows how the engine evaluates them.

Tiered quantity discount, such as four bottles for one percent off, eight for five percent, twelve for ten percent. Three or more reward tiers triggered at increasing quantity thresholds, each with a different reward value. Drives basket size on multi-unit purchases by escalating value at higher tiers — a proven pattern in beverage, supplements, pet food, and any category where customers stock up. The Order/Level promotion type makes this possible, and deploying it correctly across the fleet rewards careful platform configuration.

Category and basket-level offers

Category- and basket-level offers attach to scope the merchandising team can describe in plain language.

Targeted category discount, such as 25% off beer and wine. A flat percentage off across a defined category, member-card-gated. Lifts category sales on regulated or margin-sensitive items while building loyalty file enrollment. The configuration is straightforward when the category scope is set up to match the merchandising team's intent — and the right scope keeps new SKUs added to the category eligible automatically.

Cash reward on order value, printed as a coupon on the receipt. Spend over a threshold and a cash voucher prints on the receipt for use on the next visit. Drives return-visit frequency and basket size simultaneously. Brings four configurable pieces into harmony — the promotion record, the linked coupon, the coupon's department settings, and store-level coupon-printing system parameters — and once those four are aligned the offer runs reliably at every register every day.

Department-wide mix discount. Spend a minimum value across a department and receive a percentage off everything in that department on the ticket. Lifts category-level sales without per-item complexity. Linking to department scope rather than to a fixed item list lets this offer scale across SKU churn — new items added to the department automatically inherit the promotion.

Bundle and meal-deal offers

Bundle offers compose from items in different groups; the engine handles the cross-group attachment.

Mixed-group bundle reward. Customer buys items from multiple defined groups — for example, one from each of three groups — and receives a free item or a fixed reward. Powerful for bundled meal-deal merchandising and cross-category attachment. Group composition, trigger logic, and reward apportionment interact in ways that reward thoughtful configuration, and the result is a structured offer the merchandising team can repeat across seasons.

Bundled deal across item groups, such as buy meatloaf and get rolls free. Buy a defined main item from one group and receive a defined complementary item free from another. Drives prepared-meal and meal-solution merchandising. The link-by-item attachment and group thresholds reward precise alignment between the two groups, and a clean configuration delivers the offer cleanly across every store every week.

Bundled weighted deal, such as buy ham and get turkey free. Same bundle pattern as the previous, but operating on weighted decimal items where the threshold is by weight rather than count. Critical for deli, butcher, and seafood departments where the underlying merchandising is weight-based. The weighted-group configuration is a specialized strand of platform knowledge that JA Technology Solutions brings to every engagement.

Weighted-item offers for fresh departments

Fresh-department offers operate on actual weight; the engine evaluates each package against the weight range.

Random-weight meat BOGO with weight bounds. Buy one random-weight meat item within a defined weight range and receive one free at the matched pair's higher or lower price. Specifically supports the realities of meat, seafood, and produce departments where items are priced by weight and weights vary from package to package. Weight bounds and price-selection logic are the parts that bring this offer to life, and the configuration that handles them well is straightforward to deploy with the right platform knowledge.

Multi-group required purchase with a department component. Customer must purchase items from all of several groups — two items from each of two product groups, plus any item from a target department — before earning a fixed reward. Forces structured basket composition for category-mix campaigns. The "fixed group for promotion" flag changes the reward math in ways that field-tested platform knowledge handles cleanly.

Loyalty and member-segment offers

Customer segments link to the loyalty card so the engine can target offers without cashier overrides.

Member card points award. Points or credits posted to the member card on qualifying items. Drives loyalty engagement and supports downstream reward redemption flows that keep members returning. Points pacing — how many per dollar, per unit, or per visit — and member-scheme eligibility shape how rewarding the program feels at the register, and a well-tuned program lifts repeat visits measurably.

Senior discount delivered through a customer segment. Percentage off the order for customers tagged with a specific loyalty segment, with the discount tracked back to the loyalty server for segment-level reporting. Delivers a recurring customer-segment discount cleanly through the loyalty system, with full reporting. Segment-link configuration and loyalty-server reporting flags are the points where deep platform knowledge keeps the segment program clean and reportable from day one.

Classic buy one, get one free. Member-card-required, available across all card schemes, linked at the item level. The simplest case in the catalog, and one that benefits from the same configuration discipline as the more complex offers — clean card-scheme links, taxability flags, and department settings deliver the offer reliably to every member at every register.

Bringing the patterns to life across the fleet

One configuration, every store — the engine handles the consistency.

These fifteen are the day-to-day patterns mid-size grocery and specialty retail chains rely on, and the platform supports every one. Delivering them correctly across every store, every week — with the consistency that protects the margin built into each promotion — is where deep ENCOR expertise pays off.

Item file maintenance and audit — the unglamorous prerequisite

Automated audit compares host master against every lane on a recurring schedule, flagging drift before it touches the register.

Promotions are only as good as the item file they reference. A clean item file at the store level — accurate PLUs, current prices, correct scale flags, properly maintained linked-item structures — is what lets every promotion described above land cleanly at the register. Every chain that wants to run promotions reliably keeps its item file clean and trustworthy at the store level, not just at the host.

The PLU batch family handles item adds, updates, price changes, and full master-file loads. Two operations get used most: Batch Operation 98, the manual full item load reserved for one-shot reset scenarios, and Batch Operation 99, the routine master-file feed that drives day-to-day maintenance. Knowing which operation to use, and when, is part of the day-to-day discipline of running an ENCOR fleet at scale.

Taxability, scale flags, weight handling, WIC eligibility, mix-and-match codes, frequent-shopper fields, and linked-item structures all interact. Coordinating taxability flags with linked items keeps tax behavior correct across the basket. Aligning scale flags with the weighted promotions that depend on them keeps trigger logic predictable. The item file is a multi-dimensional configuration surface, best managed through tooling and discipline that surface every dimension clearly.

That is why automated POS item file auditing is a service I have built into the way I work with chains running ENCOR. The audit compares host master against store-level item file across every lane on a recurring schedule, surfacing drift early — items, prices, taxability, scale flags, linked-item structures, and the dozens of other categories of divergence that can accumulate between releases — so the merchandising and store systems teams can act before any of it touches the register. For a deeper treatment of multi-store item file drift, see POS Item File Sync: Keeping Stores in Sync with the Host.

What it takes to bring the full engine to life

Configuring the engine reaches in from the public surface to the field knowledge accumulated across decades of production deployments.

ENCOR's depth grew over decades. The capabilities described above accumulated as Retalix and later NCR added features in response to customer requests, regulatory changes, and competitive pressure. Layered into that depth is a body of operational expertise — the field knowledge of how the binary General Batches deliver each promotion type to POSWare, which configurations behave predictably across releases, which combinations of flags interact in non-obvious ways. That expertise lives in the practitioners who built it through direct work on production deployments.

JA Technology Solutions exists to bring that depth to retailers who want to put the engine's full capability to work. The work begins with understanding what the merchandising team wants the promotion engine to do, mapping it to the patterns the platform supports, and configuring the General Batches that deliver each promotion cleanly to every store in the fleet.

From planning data to live promotions

Planning data on the left, validated General Batches in the middle, live promotions across the fleet on the right.

Configuring promotions one at a time inside POSWare is workable for a handful at a time and slow at fleet scale. Hand-writing General Batches against vendor-spec PDFs is the old alternative — accurate when done carefully, expensive in time and attention. Most chains' merchandising teams already plan their promotions in some host environment: their merchandising platform, a planning system, an ad-period calendar, or some combination. The work that pays back is connecting that planning environment directly to ENCOR.

I build the transformation pipeline that does the connecting. Whatever form the planning data lives in today, the pipeline reads it, maps each entry to the right Enhanced Promotion structure (single-group, group, or order-level), enriches it with the supporting configuration the engine needs (group typing, time windows, segment links, funding, conflict rules, linked-item scope), and produces validated General Batches ready to load. Each batch is verified against the platform's record-format constraints before delivery so the failure modes show up at build time rather than at the register.

Both engagement models work. Build-once: I deliver the pipeline and your store-systems team runs it on whatever cadence the merchandising team plans. Ongoing service: I run the pipeline and deliver the General Batches on your cadence — weekly for ad-period drops, monthly for promotional calendars, or another rhythm that fits your operation. Same underlying pipeline either way; the difference is who runs it.

The other half of the picture

Enhanced Promotions are the input. The transaction log is the output. Both deserve real attention.

Enhanced Promotions are how value flows into the POS — the configuration that drives every transaction at every lane. There is a second half worth knowing about: how value flows out, the data record of every transaction, every void, every override, every loyalty scan.

The companion article in this pair, ENCOR (ISS45) Transaction Log Analytics: Sales, Shrink, and Fraud Detection, covers what is inside the ENCOR transaction log and the patterns it reveals when parsed correctly — sweethearting signatures, void abuse clusters, refund fraud, manager override anomalies, and the rest of the loss-prevention surface.

The business case for getting more out of what you already own

Unlocking the platform you already run is the smaller, faster, lower-risk path.

ENCOR is paid for. The license fees, back-office hardware, lane infrastructure, and years of operational tuning that keep it running are all sunk cost, already absorbed into the operating model. For chains with Enhanced Promotions in place, there is no incremental capital outlay required to begin running the patterns described above. The platform supports them today.

Replacing a POS platform across a multi-store fleet is a different conversation. A typical replacement runs two to four years from vendor selection to final conversion, costs seven or eight figures depending on scale, and asks a lot of every team that touches it. The merchandising team learns a new promotion engine, the store systems team learns new batch infrastructure, lane hardware gets re-imaged, and loss prevention waits for the new platform's data to mature before historical transaction-log analytics catch up. Every one of those transitions takes time, attention, and operational focus.

Investing modestly in unlocking the capability already present in the platform you run is the path that pays back fastest, with materially lower risk, and frees executive bandwidth for priorities that move the business immediately. A merchandising team that can run the patterns it has been asking for can drive measurable lift on next quarter's results, not three years from now.

Putting the platform you already own to its full capability also clarifies any future replacement decision, since it sharpens what "what's possible today" actually means in your environment.

How JA Technology Solutions helps

Seven service surfaces, each tied to an outcome — engaged together or as needed.

I work with grocery, convenience, and specialty retail chains running ENCOR/ISS45 across the United States. The work falls into a small number of categories, each tied to an outcome.

Promotion design and deployment — so the merchandising your team imagines launches on schedule and produces the lift it was designed for. Covers Enhanced, Group, and Order/Level promotion types, supplier-funded structures, member-card and segment targeting, and the General Batch generation that delivers it all to POSWare.

From planning data to live promotions — I build the transformation pipeline that turns your merchandising team's planning data into validated General Batches, ready to load Enhanced Promotions across every store. Engaged as a build-once project (your team runs the pipeline going forward) or as an ongoing service (I deliver the General Batches on your cadence — weekly, ad-period, or another).

Item file engineering — keeping the PLU file clean, current, and trustworthy so promotions and pricing work as intended. Covers batch design, host-to-store data flow, and the configuration of taxability, scale, WIC, mix-and-match, and linked-item structures.

Automated POS item file audit — a signature capability I bring to every engagement. The audit compares host master against store-level item file across the entire fleet on a recurring schedule, surfacing drift early so the merchandising and store systems teams can act on it before it touches the register.

Loyalty and member promotion configuration — segment targeting, card scheme management, and reward-level structures that turn the loyalty program into a real engine of repeat visits and member engagement.

Integration across the rest of the General Batch surface — departments, loyalty programs, linked items, A/R accounts, electronic WIC, and the other batch families that carry the configuration data your stores need from your host systems to POSWare.

Support contracts and on-call expertise — for chains whose internal teams want a partner on the platform-deep questions where field knowledge complements the public documentation.

I have done this work end to end at a large regional grocery chain running the platform across the fleet.

If your merchandising team has a promotion they want to run — Ask James about it. Most of the time the platform supports it; the question is connecting what the team wants to how the engine has to be configured to deliver it.

If your store systems team wants a partner on the General Batches interface, or wants ongoing visibility into item file drift across the fleet — Ask James. The chat assistant on this site is the front door to a real conversation about your specific environment, your specific platform release, and the specific patterns you want to bring live. I will follow up directly.

Have thoughts on this article? Share them.