Zoral Product Factory
Your product managers set rates, fees, terms and repayment schedules on screens, without waiting for code. Before launch, your team tests each product over years of simulated account activity. Zoral Product Factory is part of the Zoral Finance Operating System (fOS).
Zoral Product Factory works around the centre of Zoral fOS. It holds the rules of each product and runs its accounts. Zoral Decision Engine uses the same rules to set each customer’s price and limit. Zoral Data Fabric records every change and account event.
For a new bank or brand, Zoral Product Factory can be the product and account ledger. For an established bank, it runs alongside your core and posts to your general ledger.
Code-first product engines need engineers for each change. Product engines on their own leave decisions, documents and customer screens to other vendors. Zoral Product Factory shares one record with all of them.
Interest, fees and schedules are calculated as account activity happens, at very high volumes. Every event is recorded for audit.
The engine runs a banking product language, not general-purpose scripts. It is designed to keep computing costs down as volumes grow.
Your product managers change products on screens, and a second person approves. Engineers step in only where configuration ends.
Your credit committee sees how margins, fees and arrears behave over a product’s life before it approves the launch.
Your team adapts a ready template to your credit policy. The next product reuses the same rules and tests.
Your product team defines each product in a language built for banking. It uses banking terms, so the people who approve a product can read its definition.
Your product team defines each product in a language built for banking. It uses banking terms, so the people who approve a product can read its definition.
Products are defined in a domain-specific language (DSL) for banking. Definitions are readable and versioned.
A purpose-built engine runs the DSL directly, instead of general-purpose scripts.
System of record for products and accounts in a new bank or brand. Or an account-level sub-ledger that posts to your core’s general ledger.
Several brands or legal entities can run on one installation, with their accounts kept apart.
Zoral Integration Gateway links Zoral Product Factory to your core, payment systems and card processor by REST APIs, events (Kafka or RabbitMQ) or files.
Engineers add logic in JavaScript or call the bank’s own libraries. Custom screen components are written in React, through Zoral Portal Studio. Their changes are versioned and approved like any product change, and the bank sees and controls them in one console.
AWS or Azure in your chosen region, or your own data centre.
BNPL plans, asset-backed leasing, SME cash-flow lines and home finance, all with the same rules, tests and approvals.
Savings plans, term deposits and tiered rates. Your product team changes rates when margins move.
Billing cycles, fees and fee-sharing with each card partner, working with your card processor.
Your products inside partners’ apps and online checkouts. The bank keeps the credit policy, the pricing and the customer.
A new digital brand or a local credit product on the same Zoral fOS installation. Your core stays as it is.
References are available in confidence.
The Challenge
Even a simple pricing option needed custom programming in the core. Each change joined a growing backlog of IT projects.
The Solution
It moved product design to Zoral Product Factory. Its business teams now configure and launch new accounts on screens.
The Strategic Outcome
New lending products reach the market much sooner. Most product changes no longer need programming in the core.
The Challenge
Its product engine ran on heavy scripts. At peak times, transactions slowed and computing costs rose.
The Solution
It moved its product logic to Zoral Product Factory.
The Strategic Outcome
Computing costs fell. The lender then offered its products in more countries on the same platform.
No. Zoral Product Factory can run alongside your core and post to your general ledger. For a new bank or brand, it can be the product and account ledger. You decide how much moves, one product at a time.
They could. But then every rate or fee change becomes engineering work and a release, and the backlog of IT projects comes back. Here, your product managers make the change, test it on simulated accounts, and a second person approves it. Engineers still extend products where configuration ends.
Yes. Islamic and conventional products run on the same engine, with the same testing and approvals. Every version is kept with who approved it. Your Shariah board remains the authority; Zoral provides the configurable structures and the evidence trail for its review.
You do. Your data, product definitions and audit history stay yours and can be exported in standard formats.
Atelier, Zoral’s senior consulting practice, works with your teams. Its specialists have run credit, risk and operations, and the people who built the platform are part of every programme. See Product innovation, Assessment and strategy and Engineering and delivery.
Product brief
9 pages to read and share with your colleagues: what it changes, how it is controlled and audited, and how it works with the tools you already own.
Start with one product. Add the next on the same platform. A senior Zoral specialist will show how your product team would design, test and launch it.
Prefer to pick a time? Schedule a meeting
Automate lending, banking and finance operations.
London
Miami
We are on Socials
+44 20 3963 2002