Manufacturing

The manufacturing preset is for a manufacturer in the style of Odoo Manufacturing or Katana: plan production from bills of materials, buy the components through approved requisitions, inspect what arrives and what is made, handle nonconformities as cases, and keep track of who is qualified for which work. It is the erp preset plus production and quality.

ConfigCopy Anchor Link

import { defineConfig } from "better-supabase/config";

export default defineConfig({ preset: "manufacturing" });

npx better-supabase init --preset manufacturing starts a new project from it, and npx better-supabase add --preset manufacturing adds it to one you have (CLI).

BlocksCopy Anchor Link

The preset is erp plus these blocks, and whatever they require:

The preset also installs what these require, such as forms for inspection checklists and pipelines for the stages of each case kind. Each organization runs db.accounting.setup(organizationId) once, as in erp, before production books.

Options it setsCopy Anchor Link

The preset sets two options on top of erp:

export default defineConfig({
  preset: "manufacturing",
  blocks: {
    manufacturing: { options: { purchaseSuggestions: "requisition" } },
    inventory: { options: { receiptInspection: "inspection" } },
  },
});

purchaseSuggestions: "requisition" makes material requirements raise purchase requisitions that go through approvals instead of draft purchase orders (purchasing), and receiptInspection: "inspection" schedules an inspection of the default inspection kind for every receipt of a purchase order (receipts).

An entry of your own replaces the preset's keys one level deep, so setting blocks.inventory.options replaces the whole options object of the preset. Repeat receiptInspection there when you change another inventory option, or leave it out to receive stock without an inspection.

How the blocks connectCopy Anchor Link

On top of the links in erp:

A short component shows most of them at once. requirements(14) suggests buying it, and createFromRequirements raises a requisition that the purchasing manager approves. The receipt of the purchase order schedules an incoming inspection; a major nonconformity found there raises a case, and the inspection can't close until it has one. The parts that passed are consumed by a production order at their average cost, and the order's output lot remembers the receipt's lot, so a recall of that lot finds what it went into.

Qualifications don't block an operation. To keep unqualified operators off a work center, check db.qualifications.qualifiedHolders(organizationId, typeKey) for the member before startOperation, and use gaps to list who is missing a required qualification or let it lapse.

With ReUICopy Anchor Link

Each part of the app has a recipe built from ReUI components:

• Production order board: a Kanban of orders from draft to done.
• Inspection run for an incoming or in-process inspection with its checklist and findings.
• Case board and case detail for nonconformities.
• Qualification matrix.

The example app shows the material requirements under /production, with a button that creates the draft orders, next to /manufacturing, /inspections and /cases.