Skip to Content
pyxl
Build a PrototypeStart a Conversation
Regal Cinemas · Engineering

The platform was already
part of the business.

For Regal Cinemas, ecommerce, loyalty and account management were not isolated digital experiences. They were operating systems connecting customers, transactions, rewards and corporate purchasing.

Across a multi-year relationship, Pyxl designed, built, maintained and evolved critical parts of that digital ecosystem.

Enterprise commerceLoyaltyApplication engineeringPlatform support
Three Surfaces, One Ecosystem
Corporate Box Office
Regal Crown Club
REGmovies accounts
Commerce · accounts · integrations · cloud · support

Different customer experiences. One business-critical digital ecosystem.

On this pageTop ↑
The assignment

Not one website.A digital operating surface.

Regal's digital environment served more than one kind of customer and more than one kind of transaction.

Its Corporate Box Office supported business customers purchasing tickets, passes and gift products.

Its Crown Club experience allowed loyalty members to use earned rewards across Regal experiences.

Its primary customer account environment connected identity and loyalty functionality to the broader REGmovies.com experience.

Pyxl worked across those systems — designing and developing customer-facing experiences while also supporting the commerce platforms, deployment processes and technical infrastructure underneath them.

B2B commerce

Corporate purchasing needed more than a storefront.

Pyxl designed and built Regal's Corporate Box Office digital experience, supporting the part of the business responsible for selling Regal tickets, passes and gift products to corporate customers.

The work combined ecommerce experience design with the underlying application and commerce functionality required to support business purchasing.

eCommerce architectureUX / UIFrontend developmentBackend developmentMagentoAccount workflowsOrder workflowsOngoing engineering
A corporate order, end to end
AccountCatalogOrderFulfilmentReporting

A business buyer is not a consumer with a bigger basket. Purchase approval, account terms, bulk products and reporting all sit inside the same transaction, and each one is a workflow rather than a page.

What a balance has to agree with
Identity
Balance
Catalog
One understandable rewards experience

A member sees a number and a list of things it can buy. Producing that requires four systems to agree on who they are, what they have earned, what is currently redeemable and what happened after they chose.

Loyalty commerce

Points only matter when the system knows what they can buy.

Pyxl redesigned and developed Regal's Crown Club rewards-center experience, giving loyalty members a digital environment where earned credits could be used toward Regal rewards including tickets, concessions and movie-related items.

Behind the customer experience sat the more difficult engineering problem: connecting identity, balances, products, transactions and account behavior into one understandable experience.

Loyalty experienceRewards commerceAccount experienceFrontend engineeringBackend integrationMagentoUser flowsPlatform support
Identity and accounts

One customer.
More than one identity system.

Pyxl designed and developed customer account experiences for REGmovies.com, including functionality that allowed customers to authenticate using social accounts and connect external account relationships.

The work demonstrates an engineering problem that appears simple at the interface and becomes complex immediately underneath it: identity.

Customer accountsAuthenticationIdentity integrationUX / UIApplication developmentThird-party integration
One person, several credentials
Regal account
Social sign-in
External account
One resolved customer
Loyalty balance · order history · entitlements
Underneath the experience

The launch was notthe end of the engineering.

Revenue-producing digital platforms do not stop changing once they are live. Browsers change. Dependencies change. Infrastructure changes. Security requirements change. Commerce platforms release patches.

The business asks for another workflow. Traffic arrives when the release calendar says it will. Pyxl's role with Regal extended beyond project delivery into the ongoing technical operation of the platforms.

Running the platform
01Discover
  • Issue
  • Business request
  • Dependency change
02Prioritize
  • Backlog
  • Release planning
  • Application lifecycle
03Engineer
  • Bug fix
  • Enhancement
  • Integration
  • Patch
04Verify
  • QA
  • Accessibility
  • Performance
  • Security considerations
05Deploy
  • Code deployment
  • Cloud coordination
  • Release
06Operate
  • Monitor
  • Support
  • Respond
  • Repeat
Across the whole loopLevel 2 engineering supportLevel 3 engineering support

Engineering is not merely building version 1.0.

Operating scope
  • Level 2 application support
  • Level 3 application support
  • Bug resolution
  • Feature enhancements
  • Code deployment
  • Application lifecycle management
  • Release management
  • Magento patching
  • Cloud coordination
  • AWS maintenance coordination
  • Operating-system configuration and patching
  • Performance support
  • After-hours support
  • Accessibility improvements
  • Custom reporting
  • PCI-related platform maintenance

Pyxl coordinated with AWS and carried technical support responsibility. Pyxl was not Regal's sole infrastructure provider, and this page does not claim otherwise.

Existing systems

You do not always getto choose the stack.

Real engineering work often begins with architecture that already exists.

Regal's commerce properties operated within an established Magento environment and connected to infrastructure and systems that could not simply disappear because a new feature was needed.

Pyxl worked within those constraints — maintaining, patching and extending the platform while supporting the customer experiences built on top of it.

A technical partner should know when to build something new and when the job is to understand the system already carrying the business.

Existing platform supportMagento engineeringApplication maintenancePlatform enhancementRelease planningInfrastructure coordinationTechnical debt management
What made the work hard

When the platform matters,small failures are not small.

Regal's digital properties sat inside a nationally recognized consumer business with ecommerce, loyalty and customer-account experiences that customers expected to work when they needed them. That changes engineering priorities.

Deploymentbecomes operational.
Performancebecomes commercial.
Authenticationbecomes part of customer service.
A patchcan affect checkout.
An accessibility issueaffects whether someone can use the product at all.

The technical work becomes inseparable from the business using it.

Building the product matters.
Knowing how to keep it running matters too.

The ecosystem

Four layers,and concerns that cross all of them.

Illustrative view of the product ecosystem
Customer experiences
Corporate Box OfficeCrown ClubREGmovies accounts
Application services
CommerceRewardsAccounts and identityReporting
Platform
MagentoApplication logicIntegrations
Operations
AWS coordinationDeploymentRelease managementPatchingSupport
Across every layerAccessibilityQASecurity and PCI considerations
Accessibility

Part of maintaining the product.

Pyxl's Regal work also included accessibility-related improvements across its digital properties, treated as part of software quality and product maintenance rather than a one-time certification exercise.

Accessibility remediationApplication QAFrontend engineeringOngoing product improvement

Remediation work, not a certified conformance level. This page claims no WCAG conformance rating for the Regal properties and no legal certification.

The relationship

The best proof of engineering is being asked to keep engineering.

The work expanded across multiple Regal digital properties and continued beyond individual builds into ongoing platform support and technical enhancements.

That progression matters. A client can hire someone to launch a project. It keeps a technical partner when that partner understands the application well enough to help operate what comes next.

Services delivered

Engineering

One discipline. This engagement is an engineering record and the list is not padded with the marketing services Pyxl also sells.

  • Custom application development
  • eCommerce engineering
  • Magento development
  • Frontend engineering
  • Backend engineering
  • Application support
  • Platform maintenance
  • Cloud coordination
  • Application lifecycle management
  • Release management
  • Deployment
  • Accessibility
  • Custom reporting
  • Authentication and account experiences
  • Loyalty and rewards systems
Keep going

Two kinds ofengineering proof.

We do not needa blank page.

Some engineering partners are best when nothing exists yet. Pyxl is equally comfortable when the application is already live, customers are already using it and the business cannot stop while the next thing gets built.

We would like to measure which pages people read, using Google Analytics. That is the only thing these cookies do here — no advertising, no profile sold to anyone, nothing shared outside Pyxl. Say no and the site works exactly the same. Privacy policy.