Skip to content

UNIT I PROJECT: MAP A COMPLETE MINI ENTERPRISE

Design a fictional company that uses Odoo across product sales, procurement, services, manufacturing, and online channels.

This is business modeling, not Odoo configuration. Do not build records in Odoo until you can explain the flows on paper.

TABLE OF CONTENTS

PROJECT GOAL

Complete the five existing parts and include the eCommerce channel in Part 1 and the relevant sales flow. For each flow provide the seven requested elements, one numerical check, one exception with an owner, and completion evidence. Score each flow 0 for missing/incorrect, 1 for a correct sequence with missing reasoning, or 2 for a traceable explanation with quantities and exception handling. Revise each flow to 2 before moving on. The goal is a coherent business model; no paid environment, code, or deployment is required.

Design a fictional company with:

  • Sales,
  • Purchasing,
  • Warehouse,
  • Finance,
  • HR,
  • one service offering,
  • one manufactured product,
  • one eCommerce channel.

Then create four business flows:

Flow A - Lead-to-Cash

Loading diagram…
Fig 1. CRM to Accounting

Flow B - Procure-to-Pay

Loading diagram…
Fig 2. Purchase to Accounting

Flow C - Service Delivery

Loading diagram…
Fig 3. Sales to Accounting

Flow D - Manufacturing

Loading diagram…
Fig 4. Sales to Accounting

For every flow identify:

  • trigger,
  • master data,
  • transactions,
  • responsible departments,
  • application responsible for each stage,
  • output,
  • next process.

If you can do that correctly, Unit I has done its job.

PART 1: DESIGN THE COMPANY

Define at least one customer, vendor, resale item, service, manufactured product and its component recipe, plus the requested departments and employee roles. Choose a release baseline, edition, hosting assumption, and company boundary; explain how these support your flows. Assign a stable reference and unit to each product. Use the same identities when they recur across flows.

Create your fictional company profile including departments, products, services, customers, vendors, and employees.

PART 2: FLOW A - LEAD-TO-CASH

Supply opening stock, ordered quantity, price, billing policy, and payment terms. Trace demand → shortage decision → receipt if required → delivery → billing → settlement. Include sufficient-stock and supplier-delay outcomes. Explain what proof closes fulfillment and what separate proof closes the customer balance.

Map a product sale from prospect interest through payment.

PART 3: FLOW B - PROCURE-TO-PAY

Supply opening quantity, replenishment quantity, vendor price, and bill-control assumption. Identify who orders, who receives, and who verifies the bill. Test a partial receipt and a mismatched supplier bill. State whether buying is manual or triggered by configured replenishment rules.

Map a procurement cycle from need through vendor payment.

PART 4: FLOW C - SERVICE DELIVERY

Define hourly or fixed-price terms, the service product, project/tasks, responsible employee, and eligibility of recorded time. Use a complete set of hours and a rate to calculate a bill. Test non-billable work or an overrun, and identify who agrees a change with the customer.

Map a consulting or implementation sale from opportunity through billed hours.

PART 5: FLOW D - MANUFACTURING

Specify finished demand, opening finished stock, the per-unit BoM, and usable component stock. Calculate gross components, shortages, consumption, finished output, and delivery balance. Test a component shortage or rejected finished unit. Explain which actions are planned manually and which would need configured automation in Odoo.

Map a made-to-order manufacturing scenario from sales demand through delivery and invoicing.