Pricing

Pricing configurations are the rows used by the configurator to price one product opening/configuration. They are tenant-scoped and managed through the Fenestro public API.

For configurable products, do not calculate catalogue prices from base_price. Use POST /v1/products/{product_id}/pricing-configurations to manage pricing rows, then read catalogue card prices with GET /v1/categories/{category_id}/from-prices.

Endpoints

Important fields

How pricing is used

Price table formats

price_table accepts three formats.

1. Simple formula string

"100:50"

This means price = A * surface_m2 + B. For example, at 1000 x 1000 mm, 100 * 1 + 50 = 150.

2. Formula JSON with samples

{
  "type": "formule",
  "A": 100,
  "B": 50,
  "r2": 0.98,
  "widths": [1000, 1200, 1400],
  "heights": [1000, 1400, 1800],
  "echantillons": [
    { "largeur": 1000, "hauteur": 1000, "prix": 150 },
    { "largeur": 1400, "hauteur": 1800, "prix": 302 }
  ],
  "unavailable": ["1200_1400"]
}

The configurator uses A * surface_m2 + B. The unavailable array marks exact customer dimensions that must be rejected, using width_height keys.

3. Direct grid JSON

{
  "type": "table-directe",
  "modeInterpolation": "majoration",
  "widths": [1000, 1200, 1400],
  "heights": [1000, 1400, 1800],
  "prices": [
    [150, 180, 210],
    [200, null, 260],
    [245, 290, 335]
  ]
}

widths are columns, heights are rows, so prices[row][column] is the price for heights[row] and widths[column]. In the example, the 1200 x 1400 exact cell is unavailable because it is null. Use null, not 0, for unavailable cells.

modeInterpolation can be majoration, minoration, or formule. It controls customer-dimension interpolation in the configurator. The catalogue from-price shortcut still uses the cheapest filled positive cell.

Create examples

curl -X POST https://api.fenestro.io/v1/products/42/pricing-configurations \
  -H "Authorization: Bearer fen_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "leaf_count": 2,
    "fixed_part_type": "aucune",
    "opening_v1": "gauche",
    "opening_v2": "droite",
    "total_width_min": 1000,
    "total_width_max": 2200,
    "total_height_min": 1000,
    "total_height_max": 2400,
    "minimum_price": 250,
    "price_table": "{\"type\":\"table-directe\",\"modeInterpolation\":\"majoration\",\"widths\":[1000,1200],\"heights\":[1000,1400],\"prices\":[[150,180],[200,null]]}",
    "percentage_adjustment": 0,
    "active": true
  }'

From-price calculation

1. The API reads active products, active product steps, active pricing rows, and the authenticated tenant only.
2. Step snapshots can contain pricingConfig, pricing_configuration, pricingFormulas, or pricing_formulas.
3. If a step snapshot references a current pricing row id for the same product, the fresh row wins. This means patching a pricing row can update from-prices even if the step still contains an older snapshot.
4. Direct-grid rows use the cheapest filled positive cell. null and non-positive cells are ignored.
5. Formula rows use A * surface_m2 + B at total_width_min and total_height_min. If the formula cannot be evaluated, samples are used as fallback.
6. If no table/formula value exists, minimum_price is used.
7. percentage_adjustment is applied at row level.
8. Product price_adjustment_percentage is applied once after row-level pricing. Roof-window dimension flat prices are exempt, matching the existing configurator behavior.

Category from-prices

curl https://api.fenestro.io/v1/categories/12/from-prices \
  -H "Authorization: Bearer fen_live_xxxxxxxxxxxx"

{
  "42": 165,
  "43": 254,
  "44": null
}

The response is a product-id dictionary. A null value means the product is visible in the category but no active step contains enough usable pricing data.

This endpoint is for category cards and listing pages. It is not a quote endpoint for a user-entered width and height.

Common errors