EBENEER
FrançaisEnglishEspañol

THE WHOLE CHAIN

From click to CNC, with no break in the file.

Most configurators stop at the basket. This one carries on to the cutting station: the geometry that draws the picture also writes the bill of materials, the DXF and the label.

Discuss your catalogueSee the plans

ONE DERIVATION, FIVE OUTPUTS

One geometry, read by everyone.

The customer's parameters produce a single geometry. Everything else follows from it: that is what removes re-entry, and with it the transcription error.

  1. 01

    Geometric derivation

    Dimensions, material and options produce the panels, edges, drillings and grooves of one specific unit.

    GEOMETRY
  2. 02

    Real-time scene

    The scene displays that geometry, not an approximate mock-up. What the customer turns on screen is the actual part.

    3D SCENE
  3. 03

    Bill of materials

    The same geometry produces the BOM: panels to the millimetre, edging by the linear metre, hardware by the unit.

    BOM CSV / JSON
  4. 04

    Cutting and nesting

    Parts come out as DXF, nested on your panel sizes, with the cutting list and the machining sequence.

    DXF / NESTING
  5. 05

    Traceability

    Every unit receives a serial number, a label and a public page reachable by QR code.

    QR / SERIAL

01PRICING

A price nobody can rewrite.

The displayed amount is computed by the server from your grid: material, surface, metres of edging, hardware, labour, margin. The browser computes nothing, it asks. At checkout the price is recomputed and compared: the slightest gap and the order is refused.

  • Price grid and purchase costs are never sent to the browser.
  • Checkout re-comparison: any gap blocks the payment.
  • Your margins never leave your instance.
TOLERATED GAP: 0 · ORDER BLOCKED

02RULES

What cannot be built cannot be ordered.

Maximum shelf span, minimum back thickness, edging length, compatibility between a material and an option: your constraints are written as declarative rules held in the database, and they change without a redeployment. The engine is fail-closed — in case of doubt, it refuses.

  • Your workshop constraints, encoded with your workshop manager.
  • Fail-closed: a missing or ambiguous rule blocks, it never allows.
  • The refusal is explained to the customer in plain words, not in code.
DECLARATIVE ENGINE · FAIL-CLOSED

03ORDER PACK

The workshop receives a file, not an email.

With every order the pack is generated: a digital-twin manifest of the configuration, the BOM in CSV and JSON, a PDF cutting list, the nesting DXF and a sheet of QR labels. The cutting station opens a complete, dated, versioned file.

  • Full manifest: every chosen parameter, time-stamped and versioned.
  • BOM in CSV for your ERP, in JSON for your own tools.
  • Labels and /e/[serial] QR codes: one unit made, one public page.

01MANIFEST

02BOM

03PDF SHEET

04DXF

05LABELS

ORDER PACKebeneer configurator
CNC APPROVED
Close-up of machining on a CNC router: the cutter engaged in a panel, chips and cutting marks.
MACHINING · Ø 8 CUTTER · FINISHING PASSCNC APPROVED

04COMMERCE

Native WooCommerce, plus a complete mock mode.

The commerce layer is isolated. The configurator pushes the configuration into WooCommerce with the server price and the manifest attached to the order line. Mock mode replays the entire purchase journey with no shop connected — enough to sell in a meeting before you have opened a payment account.

  • Installed on your existing WooCommerce, with no shop migration.
  • A verification plugin that locks the price at checkout.
  • Mock mode: full journey through to confirmation, with no money taken.
WOOCOMMERCE · PRICE CHECK AT CHECKOUT

05ISOLATION

One instance per workshop.

Every customer gets their own instance: their database, their rules, their catalogue, their costs. Separation is enforced row by row by the database, not by the application alone. Your purchase prices are never serialised to a browser.

  • Dedicated instance: your catalogue is not pooled with anyone else's.
  • Row-level separation, enforced by the database itself.
  • Reversibility: the catalogue, the rules and the orders are yours.
DEDICATED INSTANCE · RLS · COSTS NEVER EXPOSED

STATED LIMITS

What we do not promise.

A supplier with no limits has no product. These are the ones that matter before you sign.

  1. 01

    One instance, one language, one currency.

    Visible strings are translated, but a deployment carries one language and one currency at a time. Two markets means two instances, priced as such. That is the cost of coherence: the server price remains the only truth.

  2. 02

    WooCommerce is required to take payment.

    Checking the price at payment time requires a plugin on the shop side, and that plugin exists for WooCommerce. If you have no shop, we install one. We do not promise Shopify: the adapter is not written, and we would rather say so before you sign.

  3. 03

    Materials require physical samples.

    We do not build a colour from a trade name. You send the samples, we photograph and calibrate them, then we validate the result next to the real part.

WHAT COMES NEXT

Your know-how encoded, not replaced.

The rules are yours, the price grid is yours, and the production pack speaks the language of your workshop.

Discuss your catalogue