Appearance
OSERP™ Industry Context Library
This library explains the business context behind OSERP records. It is written for end users, consultants, trainers, and AI retrieval. Industry context is not a statutory rulebook: tax, payroll, revenue recognition, fund accounting, privacy, and sector regulation must be reviewed for the country and release being implemented.
The common OSERP lens
Every industry can be understood through six questions:
- Who owns the business event? Company, branch, project, programme, or channel?
- What is the master record? Item, service, customer, supplier, employee, asset, contract, or grant?
- What changes? Quantity, money, commitment, status, entitlement, or approval?
- What is the evidence? Source document, receipt, approval, settlement, report, or audit event?
- What can go wrong? Shortage, duplicate, overrun, wrong tax, failed payment, privacy breach, or period lock?
- What should management measure? Service level, margin, cash, utilisation, quality, risk, or impact?
Retail and distribution
Operating model: Purchase at scale, hold stock in warehouses, replenish branches, sell through stores and channels, and reconcile money at high volume.
Business vocabulary: SKU, barcode, assortment, planogram, pack size, case, batch, expiry, replenishment, allocation, reservation, markdown, shrinkage, landed cost, sell-through, and stock-out.
Core masters: Item, unit conversion, brand, category, supplier, customer group, branch, warehouse, bin, price list, tax category, batch, loyalty profile, and payment method.
Lifecycle: Forecast/demand → purchase → receipt → put-away → allocation/transfer → POS or online order → pick/dispatch → payment → return → reconciliation → replenishment.
OSERP context: Item code and barcode identify the product; warehouse and branch identify physical ownership/location; reservation separates promised quantity from free quantity; price source explains why a customer sees a value; batch and expiry protect saleability; payment clearing separates authorisation from settlement.
Management KPIs: Sales per square metre, gross margin, sell-through, stock-out rate, inventory days, shrinkage, stock accuracy, basket value, return rate, order-to-dispatch time, and branch contribution.
Controls: Maker-checker for price and refund changes, transfer dispatch/receipt, cycle count approval, batch quarantine, cashier shift close, payment settlement matching, period lock, and branch-scoped access.
Implementation questions: Is stock owned by the legal company or branch? Does MRP apply? Are prices tax-inclusive? Which channel reserves first? What is the cost of an inter-company transfer? Which returns become saleable stock?
Manufacturing
Operating model: Convert materials into finished goods through planned or make-to-order production, while controlling yield, quality, cost, capacity, and traceability.
Business vocabulary: BOM, routing, work order, issue, backflush, work-in-progress, yield, scrap, rework, co-product, by-product, batch genealogy, serial number, quality hold, standard cost, and variance.
Core masters: Raw material, semi-finished item, finished item, BOM version, routing/work centre, operation, batch, serial, warehouse, substitute component, labour rate, overhead rule, and quality status.
Lifecycle: Demand/plan → material availability → work order → component issue → operation/labour → quality check → finished receipt → quarantine/release → dispatch → variance and close.
OSERP context: Unit precision matters for recipes and conversions; a work order explains why stock moved; scrap must carry a reason; quarantine prevents failed goods from becoming available; finished receipt and cost roll-up connect physical output to accounting evidence.
Management KPIs: Overall equipment effectiveness, yield, scrap percentage, first-pass quality, schedule adherence, material variance, capacity utilisation, on-time delivery, and recall trace time.
Controls: BOM version approval, substitute approval, restricted scrap reasons, batch/serial genealogy, quality release, negative-stock prevention, standard-cost review, and production posting permissions.
Implementation questions: Is production currently supported or an extension? Which costing method is authoritative? Are labour and overhead posted at operation, work order, or period level? How are co-products and rework valued?
Professional services
Operating model: Sell expertise and outcomes rather than physical stock; convert people’s time and expenses into milestones, retainers, invoices, and receivables.
Business vocabulary: Engagement, scope, statement of work, billable, non-billable, utilisation, retainer, milestone, time cap, write-off, change request, work-in-progress, and revenue schedule.
Core masters: Customer, project, contract, work package, employee/consultant, rate card, cost centre, expense category, milestone, currency, tax treatment, and approval matrix.
Lifecycle: Opportunity → contract/scope → budget → resource assignment → time/expense capture → approval → milestone or time invoice → collection → margin and utilisation review.
OSERP context: A project dimension preserves the reason for a cost; approved time is not automatically an invoice; an invoice milestone is not proof of revenue recognition; foreign-currency rates need an explicit policy; unbilled work needs an ageing and recovery path.
Management KPIs: Utilisation, realisation, billable leakage, days-to-invoice, backlog, project gross margin, budget burn, overdue receivables, and forecast accuracy.
Controls: Timesheet approval, expense receipt evidence, rate-card versioning, change-order approval, write-off authority, project access, credit limits, and period lock.
Implementation questions: Is revenue recognised on time, milestone, delivery, or another approved policy? Which hours are billable? Can rates differ by country? What evidence is required before an invoice is issued?
Hospitality
Operating model: Sell perishable services and experiences—rooms, food, events, and packages—while managing capacity, deposits, consumption, service quality, and rapid settlement.
Business vocabulary: Folio, occupancy, ADR, RevPAR, no-show, cancellation, deposit, package, cover, outlet, wastage, comp, tips, banquet event order, and settlement.
Core masters: Property/branch, room or venue, service item, recipe/stock item, guest/corporate account, package, rate plan, tax category, payment method, event, and deposit type.
Lifecycle: Reservation → deposit → service consumption → stock issue → folio charge → package/tax allocation → checkout → payment/receivable → shift close → wastage and margin review.
OSERP context: A room charge is a service event; restaurant ingredients are stock consumption; a deposit is not automatically revenue; a folio can contain multiple currencies or tenders; cancellation and refund need their own evidence.
Management KPIs: Occupancy, ADR, RevPAR, outlet margin, food-cost percentage, wastage, average checkout time, folio exception rate, settlement variance, and event conversion.
Controls: Deposit and refund approval, outlet shift close, comp authorisation, recipe versioning, wastage reason, guest privacy, split tender reconciliation, and period lock.
Implementation questions: Which services create inventory consumption? How are packages allocated? Which country or property tax rules apply? Does the folio integrate with a reservation or property-management system?
E-commerce
Operating model: Publish a digital catalogue, acquire orders continuously, reserve and fulfil from distributed stock, collect digitally, and manage returns and marketplace settlement.
Business vocabulary: Catalogue, variant, channel, reservation, fulfilment node, pick/pack, promised date, gateway, capture, authorisation, chargeback, return disposition, commission, and payout.
Core masters: Product, variant, image/content, channel, price list, warehouse, delivery zone, tax category, payment gateway, customer, return reason, and marketplace account.
Lifecycle: Catalogue publication → browse/cart → order → reservation → payment authorisation/capture → fulfilment → delivery → return/refund → gateway/marketplace reconciliation.
OSERP context: A published product is not necessarily sellable; available stock must exclude reservations; payment state and fulfilment state differ; webhook idempotency prevents duplicates; a returned item needs inspection before stock is released.
Management KPIs: Conversion, average order value, cancellation, fulfilment accuracy, on-time dispatch, return rate, refund cycle, contribution margin after commission, and reserved-stock age.
Controls: Catalogue approval, price publication, stock reservation expiry, gateway signature validation, idempotency key, refund authority, return inspection, privacy scope, and settlement reconciliation.
Implementation questions: Which system owns the catalogue? Which node fulfils? How are split shipments represented? When is revenue recognised? How are marketplace commissions and chargebacks posted?
Projects and contracting
Operating model: Deliver a contracted outcome over time using budgets, commitments, site costs, progress evidence, retention, variations, and forecasts.
Business vocabulary: Contract, BOQ, work package, site, subcontractor, committed cost, progress certificate, retention, variation, claim, mobilisation advance, WIP, and cost-to-complete.
Core masters: Customer, contract, project, site, budget, cost code, subcontractor, material, equipment, milestone, retention rule, currency, and approval role.
Lifecycle: Bid/contract → budget → procurement commitment → site receipt/issue → work progress → certification → invoice/retention → collection → forecast and close.
OSERP context: A purchase order is a commitment before it is an actual cost; a progress certificate is evidence for billing; retention changes cash timing; a variation must be versioned; forecast values must not be confused with posted ledger facts.
Management KPIs: Cost-to-complete variance, committed-cost coverage, earned-value trend, gross margin, change-order cycle, retention ageing, cash conversion, and schedule adherence.
Controls: Contract version approval, budget release, purchase commitment, site receipt, progress certification, retention review, subcontractor validation, change control, and project access.
Implementation questions: Which costs are capital, expense, or WIP? Who certifies progress? How are retention and advances settled? Can one contract span companies or currencies? Which forecast is approved?
Education
Operating model: Enrol learners into programmes, deliver teaching, collect fees from learners or sponsors, pay instructors, and report outcomes while protecting personal data.
Business vocabulary: Cohort, intake, sponsor, scholarship, instalment, attendance, completion, deferral, withdrawal, refund, instructor, programme, and cost per learner.
Core masters: Learner, sponsor, programme, course, cohort, instructor, fee plan, scholarship, calendar, campus/branch, currency, and privacy role.
Lifecycle: Programme setup → marketing/enrolment → scholarship approval → invoice → instalment collection → attendance/completion → instructor expense → refund/deferral → programme report.
OSERP context: Learner identity and sponsor billing may have different scopes; a scholarship changes the receivable but needs approval; attendance is evidence, not automatically revenue; personal data should never enter public training examples.
Management KPIs: Enrolment conversion, collection rate, attendance, completion, refund/withdrawal rate, cost per learner, instructor utilisation, programme margin, and sponsor ageing.
Controls: Privacy-by-role, scholarship authority, refund policy, attendance edit history, sponsor credit control, instructor expense approval, and audit logging.
Implementation questions: Which system owns attendance or learning content? What event makes a fee earned? How are grants or sponsors restricted? What retention and deletion rules apply to learner data?
Nonprofit operations
Operating model: Convert donations and restricted grants into accountable programmes, procurement, distribution, services, and impact reporting.
Business vocabulary: Donor, grant, restriction, fund, programme, beneficiary, in-kind donation, appeal, overhead, restricted balance, distribution, impact metric, and stewardship.
Core masters: Donor, grant, fund, programme, beneficiary scope, item, supplier, warehouse, budget, cost centre, currency, and approval role.
Lifecycle: Grant/donation → restriction and budget → purchase or in-kind receipt → warehouse/quarantine → programme distribution → expense → donor report → reconciliation and audit.
OSERP context: A restricted grant is not interchangeable with unrestricted cash; stock distribution needs a programme reference; donated goods need valuation policy; impact metrics and accounting values should be related but not confused.
Management KPIs: Grant-to-programme traceability, cost per beneficiary, budget variance, distribution timeliness, restricted balance, donor-report days, overhead ratio, and audit retrieval time.
Controls: Grant restriction, budget approval, procurement threshold, distribution authorisation, beneficiary privacy, conflict-of-interest declaration, donor report review, and audit trail.
Implementation questions: Which fund-accounting rules apply? How are in-kind goods valued? What evidence supports beneficiary counts? Which reports are donor-facing versus statutory? How are unused restricted balances returned?
Use this context with OSERP Atlas
When answering an industry question, identify the industry context first, then locate the OSERP screen, field, permission, and side effect. If a business rule is not evidenced in the deployed release, say unknown or requires configuration/review. Never turn an illustrative case, KPI target, or local accounting assumption into a product guarantee.