@revenexx/node 0.1.0 → 0.1.1

package/dist/services/health.d.ts

@@ -3,6 +3,15 @@ import '../models.js';
 import '../enums/address-type-row-tone.js';
 import '../enums/address-type-row-create-request-tone.js';
 import '../enums/address-type-row-update-request-tone.js';
+import '../enums/approval-rule-approver-type.js';
+import '../enums/approval-rule-condition.js';
+import '../enums/approval-rule-effect.js';
+import '../enums/approval-rule-create-request-approver-type.js';
+import '../enums/approval-rule-create-request-condition.js';
+import '../enums/approval-rule-create-request-effect.js';
+import '../enums/approval-rule-update-request-approver-type.js';
+import '../enums/approval-rule-update-request-condition.js';
+import '../enums/approval-rule-update-request-effect.js';
 import '../enums/assets-source.js';
 import '../enums/attribute-value-bucket.js';
 import '../enums/auth-mail-source.js';
@@ -116,6 +125,8 @@ import '../enums/payment-term-tone.js';
 import '../enums/payment-term-create-request-tone.js';
 import '../enums/payment-term-update-request-tone.js';
 import '../enums/payment-vocabulary-tone.js';
+import '../enums/pending-approval-approver-type.js';
+import '../enums/pending-approval-status.js';
 import '../enums/price-ending-rule.js';
 import '../enums/price-entries-adjust-response-rounding.js';
 import '../enums/price-entries-adjust-response-rounding-mode.js';
@@ -138,6 +149,11 @@ import '../enums/product-grid-column-source.js';
 import '../enums/product-label-source.js';
 import '../enums/product-label-attribute-source.js';
 import '../enums/products-kind.js';
+import '../enums/purchase-request-status.js';
+import '../enums/purchase-request-event-name.js';
+import '../enums/purchase-request-item-type.js';
+import '../enums/purchase-request-item-create-request-type.js';
+import '../enums/purchase-request-item-update-request-type.js';
 import '../enums/reorder-point-source.js';
 import '../enums/reservation-status.js';
 import '../enums/price-on-request-reason.js';
@@ -175,6 +191,8 @@ import '../enums/shipping-weight-unit-row-tone.js';
 import '../enums/shipping-weight-unit-update-request-tone.js';
 import '../enums/stock-movement-type.js';
 import '../enums/store-asset-request-visibility.js';
+import '../enums/submit-item-type.js';
+import '../enums/submit-result-outcome.js';
 import '../enums/validation-failed-response-status.js';
 import '../enums/vocabulary-default-tone.js';
 import '../enums/vocabulary-source.js';

package/dist/services/inventories-locations.d.mts

@@ -6,6 +6,15 @@ import '../query.mjs';
 import '../enums/address-type-row-tone.mjs';
 import '../enums/address-type-row-create-request-tone.mjs';
 import '../enums/address-type-row-update-request-tone.mjs';
+import '../enums/approval-rule-approver-type.mjs';
+import '../enums/approval-rule-condition.mjs';
+import '../enums/approval-rule-effect.mjs';
+import '../enums/approval-rule-create-request-approver-type.mjs';
+import '../enums/approval-rule-create-request-condition.mjs';
+import '../enums/approval-rule-create-request-effect.mjs';
+import '../enums/approval-rule-update-request-approver-type.mjs';
+import '../enums/approval-rule-update-request-condition.mjs';
+import '../enums/approval-rule-update-request-effect.mjs';
 import '../enums/assets-source.mjs';
 import '../enums/attribute-value-bucket.mjs';
 import '../enums/auth-mail-source.mjs';
@@ -118,6 +127,8 @@ import '../enums/payment-term-tone.mjs';
 import '../enums/payment-term-create-request-tone.mjs';
 import '../enums/payment-term-update-request-tone.mjs';
 import '../enums/payment-vocabulary-tone.mjs';
+import '../enums/pending-approval-approver-type.mjs';
+import '../enums/pending-approval-status.mjs';
 import '../enums/price-ending-rule.mjs';
 import '../enums/price-entries-adjust-response-rounding.mjs';
 import '../enums/price-entries-adjust-response-rounding-mode.mjs';
@@ -140,6 +151,11 @@ import '../enums/product-grid-column-source.mjs';
 import '../enums/product-label-source.mjs';
 import '../enums/product-label-attribute-source.mjs';
 import '../enums/products-kind.mjs';
+import '../enums/purchase-request-status.mjs';
+import '../enums/purchase-request-event-name.mjs';
+import '../enums/purchase-request-item-type.mjs';
+import '../enums/purchase-request-item-create-request-type.mjs';
+import '../enums/purchase-request-item-update-request-type.mjs';
 import '../enums/reorder-point-source.mjs';
 import '../enums/reservation-status.mjs';
 import '../enums/price-on-request-reason.mjs';
@@ -177,6 +193,8 @@ import '../enums/shipping-weight-unit-row-tone.mjs';
 import '../enums/shipping-weight-unit-update-request-tone.mjs';
 import '../enums/stock-movement-type.mjs';
 import '../enums/store-asset-request-visibility.mjs';
+import '../enums/submit-item-type.mjs';
+import '../enums/submit-result-outcome.mjs';
 import '../enums/validation-failed-response-status.mjs';
 import '../enums/vocabulary-default-tone.mjs';
 import '../enums/vocabulary-source.mjs';
@@ -245,7 +263,7 @@ declare class InventoriesLocations {
      * @param {string} params.createdAt - Exact-match filter on `created_at`. When the row was created.
      * @param {string} params.updatedAt - Exact-match filter on `updated_at`. When the row was last written.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      */
     inventoriesLocationsList(params?: {
         limit?: number;
@@ -262,7 +280,7 @@ declare class InventoriesLocations {
         metadata?: string;
         createdAt?: string;
         updatedAt?: string;
-    }): Promise<Models.Error>;
+    }): Promise<{}>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the list a `location_code` is resolved against on every stock call, so it is the first thing to read when a receipt answers "unknown location". It answers no quantities at all — how much is at a location is GET /inventories/stock?location_id=…, and what may still be sold is POST /inventories/availability. Filter `?enabled=true` for the operational subset: availability and reserve only ever look at enabled locations, so a disabled one is invisible to a shop while keeping every row that points at it.
      *
@@ -281,10 +299,10 @@ declare class InventoriesLocations {
      * @param {string} createdAt - Exact-match filter on `created_at`. When the row was created.
      * @param {string} updatedAt - Exact-match filter on `updated_at`. When the row was last written.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsList(limit?: number, offset?: number, order?: string, id?: string, code?: string, name?: string, labels?: string, type?: InventoriesLocationsListType, priority?: number, enabled?: boolean, address?: string, metadata?: string, createdAt?: string, updatedAt?: string): Promise<Models.Error>;
+    inventoriesLocationsList(limit?: number, offset?: number, order?: string, id?: string, code?: string, name?: string, labels?: string, type?: InventoriesLocationsListType, priority?: number, enabled?: boolean, address?: string, metadata?: string, createdAt?: string, updatedAt?: string): Promise<{}>;
     /**
      * Registers a new place stock can be kept, and `type` says what kind of place it is: a warehouse of your own, a store whose shop floor a click-and-collect order draws on, a dropship supplier whose stock this row only tracks, or a virtual bucket that is not a building at all — pre-orders, consignment, a quarantine shelf. A create cannot omit `code` and `name`; every other column is optional or defaulted by the database. Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert. A new location starts EMPTY and creating one moves nothing: stock arrives through POST /inventories/receive, or is transferred by two adjustments, one negative at the old location and one positive here. Mind the two columns that are not decoration — `priority` decides where a reservation is served from before `type` ever does (nothing branches on `type`), and `enabled` defaults to true, so a location created for a warehouse that has not opened yet starts being offered by availability and reserve immediately.
      *
@@ -297,7 +315,7 @@ declare class InventoriesLocations {
      * @param {number} params.priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} params.type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsCreate(params: {
         code: string;
@@ -308,7 +326,7 @@ declare class InventoriesLocations {
         metadata?: object;
         priority?: number;
         type?: LocationType;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * Registers a new place stock can be kept, and `type` says what kind of place it is: a warehouse of your own, a store whose shop floor a click-and-collect order draws on, a dropship supplier whose stock this row only tracks, or a virtual bucket that is not a building at all — pre-orders, consignment, a quarantine shelf. A create cannot omit `code` and `name`; every other column is optional or defaulted by the database. Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert. A new location starts EMPTY and creating one moves nothing: stock arrives through POST /inventories/receive, or is transferred by two adjustments, one negative at the old location and one positive here. Mind the two columns that are not decoration — `priority` decides where a reservation is served from before `type` ever does (nothing branches on `type`), and `enabled` defaults to true, so a location created for a warehouse that has not opened yet starts being offered by availability and reserve immediately.
      *
@@ -321,10 +339,10 @@ declare class InventoriesLocations {
      * @param {number} priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsCreate(code: string, name: string, address?: object, enabled?: boolean, labels?: object, metadata?: object, priority?: number, type?: LocationType): Promise<Models.Error>;
+    inventoriesLocationsCreate(code: string, name: string, address?: object, enabled?: boolean, labels?: object, metadata?: object, priority?: number, type?: LocationType): Promise<Models.Location>;
     /**
      * Gives a tenant its first location, `main`, so the stock calls have somewhere to book into: `receive`, `adjust` and `restock` fall back to the `default_location_code` setting when a caller names no `location_code`, and a tenant with no location at all answers 400 on its first receipt. The platform already runs this on `app.installed`, so calling it by hand is the repair for an install that predates the event or a `main` somebody deleted. Idempotent by CODE, not by contents: a location already carrying that code is reported under `existing` and is NOT touched, so a renamed or disabled `main` stays renamed and disabled. It creates nothing else and never removes a location.
      *
@@ -337,39 +355,39 @@ declare class InventoriesLocations {
      *
      * @param {string} params.id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      */
     inventoriesLocationsDelete(params: {
         id: string;
-    }): Promise<Models.Error>;
+    }): Promise<{}>;
     /**
      * Deleting one takes every `stock_levels` row that points at it with it — the foreign key decides that, not this route. What the database does NOT clean up is everything else carrying the same id: `stock_movements.location_id` and `reservations.location_id` are plain uuid columns and not foreign keys, so those rows stay exactly where they are, pointing at a row that no longer exists, and nothing nulls the pointer. That asymmetry destroys the balances and keeps everything that refers to them, so the route REFUSES while anything still depends on the location and answers 409 with the count — taken here rather than left to whoever is about to click delete, because a client that pre-counts asks a second question whose answer disagrees the moment a receipt lands between the two calls. Two things block it. A stock row still carrying `on_hand`: the cascade would destroy recorded inventory and nothing in this app ever replays the ledger to rebuild a balance, so there is no undo. And a reservation still `active`: a promise to a customer must not outlive the row backing it — such a hold used to survive its stock row, after which /release lowered no `reserved` and still wrote its `release` booking, and /commit booked the whole quantity as a shortfall, neither of them an error. A stock row at zero does not block: it records no quantity. HISTORY never blocks, and is never deleted either — a movement is an accounting record and removing one would falsify it, so the bookings stay, naming a location that no longer resolves, BY DESIGN. A location that once had traffic and now holds nothing is exactly what a merchant closes. To get past the 409, adjust the stock to zero and release or commit the holds; where the location is merely out of service, PUT `enabled: false` keeps every row and can be undone.
      *
      * @param {string} id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsDelete(id: string): Promise<Models.Error>;
+    inventoriesLocationsDelete(id: string): Promise<{}>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the route that turns an id back into a place: `location_id` is on every stock row, every ledger booking and every reservation, and none of them carries the code or the name. Reading it also answers the two questions those rows raise — whether the location is still `enabled` (a disabled one is skipped by availability and reserve while its stock stays exactly where it is) and where its `priority` puts it when the allocation strategy picks somewhere to reserve from.
      *
      * @param {string} params.id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsGet(params: {
         id: string;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the route that turns an id back into a place: `location_id` is on every stock row, every ledger booking and every reservation, and none of them carries the code or the name. Reading it also answers the two questions those rows raise — whether the location is still `enabled` (a disabled one is skipped by availability and reserve while its stock stays exactly where it is) and where its `priority` puts it when the allocation strategy picks somewhere to reserve from.
      *
      * @param {string} id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsGet(id: string): Promise<Models.Error>;
+    inventoriesLocationsGet(id: string): Promise<Models.Location>;
     /**
      * Partial update: send the fields that change. The one with consequences is `enabled` — setting it to false is how a location is taken out of service WITHOUT losing anything. Availability and reserve stop looking at it, so its stock stops being sellable, while every stock row, ledger booking and reservation that points at it survives untouched and comes back the moment it is enabled again. That is the reversible alternative to DELETE, which is not reversible at all. Changing `code` is the other sharp edge: rows keep their `location_id` so nothing moves, but every caller that names the old code in `location_code` starts getting 400 "unknown location". Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert.
      *
@@ -383,7 +401,7 @@ declare class InventoriesLocations {
      * @param {number} params.priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} params.type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsUpdate(params: {
         id: string;
@@ -395,7 +413,7 @@ declare class InventoriesLocations {
         name?: string;
         priority?: number;
         type?: LocationType;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * Partial update: send the fields that change. The one with consequences is `enabled` — setting it to false is how a location is taken out of service WITHOUT losing anything. Availability and reserve stop looking at it, so its stock stops being sellable, while every stock row, ledger booking and reservation that points at it survives untouched and comes back the moment it is enabled again. That is the reversible alternative to DELETE, which is not reversible at all. Changing `code` is the other sharp edge: rows keep their `location_id` so nothing moves, but every caller that names the old code in `location_code` starts getting 400 "unknown location". Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert.
      *
@@ -409,10 +427,10 @@ declare class InventoriesLocations {
      * @param {number} priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsUpdate(id: string, address?: object, code?: string, enabled?: boolean, labels?: object, metadata?: object, name?: string, priority?: number, type?: LocationType): Promise<Models.Error>;
+    inventoriesLocationsUpdate(id: string, address?: object, code?: string, enabled?: boolean, labels?: object, metadata?: object, name?: string, priority?: number, type?: LocationType): Promise<Models.Location>;
 }
 
 export { InventoriesLocations };

package/dist/services/inventories-locations.d.ts

@@ -6,6 +6,15 @@ import '../query.js';
 import '../enums/address-type-row-tone.js';
 import '../enums/address-type-row-create-request-tone.js';
 import '../enums/address-type-row-update-request-tone.js';
+import '../enums/approval-rule-approver-type.js';
+import '../enums/approval-rule-condition.js';
+import '../enums/approval-rule-effect.js';
+import '../enums/approval-rule-create-request-approver-type.js';
+import '../enums/approval-rule-create-request-condition.js';
+import '../enums/approval-rule-create-request-effect.js';
+import '../enums/approval-rule-update-request-approver-type.js';
+import '../enums/approval-rule-update-request-condition.js';
+import '../enums/approval-rule-update-request-effect.js';
 import '../enums/assets-source.js';
 import '../enums/attribute-value-bucket.js';
 import '../enums/auth-mail-source.js';
@@ -118,6 +127,8 @@ import '../enums/payment-term-tone.js';
 import '../enums/payment-term-create-request-tone.js';
 import '../enums/payment-term-update-request-tone.js';
 import '../enums/payment-vocabulary-tone.js';
+import '../enums/pending-approval-approver-type.js';
+import '../enums/pending-approval-status.js';
 import '../enums/price-ending-rule.js';
 import '../enums/price-entries-adjust-response-rounding.js';
 import '../enums/price-entries-adjust-response-rounding-mode.js';
@@ -140,6 +151,11 @@ import '../enums/product-grid-column-source.js';
 import '../enums/product-label-source.js';
 import '../enums/product-label-attribute-source.js';
 import '../enums/products-kind.js';
+import '../enums/purchase-request-status.js';
+import '../enums/purchase-request-event-name.js';
+import '../enums/purchase-request-item-type.js';
+import '../enums/purchase-request-item-create-request-type.js';
+import '../enums/purchase-request-item-update-request-type.js';
 import '../enums/reorder-point-source.js';
 import '../enums/reservation-status.js';
 import '../enums/price-on-request-reason.js';
@@ -177,6 +193,8 @@ import '../enums/shipping-weight-unit-row-tone.js';
 import '../enums/shipping-weight-unit-update-request-tone.js';
 import '../enums/stock-movement-type.js';
 import '../enums/store-asset-request-visibility.js';
+import '../enums/submit-item-type.js';
+import '../enums/submit-result-outcome.js';
 import '../enums/validation-failed-response-status.js';
 import '../enums/vocabulary-default-tone.js';
 import '../enums/vocabulary-source.js';
@@ -245,7 +263,7 @@ declare class InventoriesLocations {
      * @param {string} params.createdAt - Exact-match filter on `created_at`. When the row was created.
      * @param {string} params.updatedAt - Exact-match filter on `updated_at`. When the row was last written.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      */
     inventoriesLocationsList(params?: {
         limit?: number;
@@ -262,7 +280,7 @@ declare class InventoriesLocations {
         metadata?: string;
         createdAt?: string;
         updatedAt?: string;
-    }): Promise<Models.Error>;
+    }): Promise<{}>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the list a `location_code` is resolved against on every stock call, so it is the first thing to read when a receipt answers "unknown location". It answers no quantities at all — how much is at a location is GET /inventories/stock?location_id=…, and what may still be sold is POST /inventories/availability. Filter `?enabled=true` for the operational subset: availability and reserve only ever look at enabled locations, so a disabled one is invisible to a shop while keeping every row that points at it.
      *
@@ -281,10 +299,10 @@ declare class InventoriesLocations {
      * @param {string} createdAt - Exact-match filter on `created_at`. When the row was created.
      * @param {string} updatedAt - Exact-match filter on `updated_at`. When the row was last written.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsList(limit?: number, offset?: number, order?: string, id?: string, code?: string, name?: string, labels?: string, type?: InventoriesLocationsListType, priority?: number, enabled?: boolean, address?: string, metadata?: string, createdAt?: string, updatedAt?: string): Promise<Models.Error>;
+    inventoriesLocationsList(limit?: number, offset?: number, order?: string, id?: string, code?: string, name?: string, labels?: string, type?: InventoriesLocationsListType, priority?: number, enabled?: boolean, address?: string, metadata?: string, createdAt?: string, updatedAt?: string): Promise<{}>;
     /**
      * Registers a new place stock can be kept, and `type` says what kind of place it is: a warehouse of your own, a store whose shop floor a click-and-collect order draws on, a dropship supplier whose stock this row only tracks, or a virtual bucket that is not a building at all — pre-orders, consignment, a quarantine shelf. A create cannot omit `code` and `name`; every other column is optional or defaulted by the database. Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert. A new location starts EMPTY and creating one moves nothing: stock arrives through POST /inventories/receive, or is transferred by two adjustments, one negative at the old location and one positive here. Mind the two columns that are not decoration — `priority` decides where a reservation is served from before `type` ever does (nothing branches on `type`), and `enabled` defaults to true, so a location created for a warehouse that has not opened yet starts being offered by availability and reserve immediately.
      *
@@ -297,7 +315,7 @@ declare class InventoriesLocations {
      * @param {number} params.priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} params.type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsCreate(params: {
         code: string;
@@ -308,7 +326,7 @@ declare class InventoriesLocations {
         metadata?: object;
         priority?: number;
         type?: LocationType;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * Registers a new place stock can be kept, and `type` says what kind of place it is: a warehouse of your own, a store whose shop floor a click-and-collect order draws on, a dropship supplier whose stock this row only tracks, or a virtual bucket that is not a building at all — pre-orders, consignment, a quarantine shelf. A create cannot omit `code` and `name`; every other column is optional or defaulted by the database. Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert. A new location starts EMPTY and creating one moves nothing: stock arrives through POST /inventories/receive, or is transferred by two adjustments, one negative at the old location and one positive here. Mind the two columns that are not decoration — `priority` decides where a reservation is served from before `type` ever does (nothing branches on `type`), and `enabled` defaults to true, so a location created for a warehouse that has not opened yet starts being offered by availability and reserve immediately.
      *
@@ -321,10 +339,10 @@ declare class InventoriesLocations {
      * @param {number} priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsCreate(code: string, name: string, address?: object, enabled?: boolean, labels?: object, metadata?: object, priority?: number, type?: LocationType): Promise<Models.Error>;
+    inventoriesLocationsCreate(code: string, name: string, address?: object, enabled?: boolean, labels?: object, metadata?: object, priority?: number, type?: LocationType): Promise<Models.Location>;
     /**
      * Gives a tenant its first location, `main`, so the stock calls have somewhere to book into: `receive`, `adjust` and `restock` fall back to the `default_location_code` setting when a caller names no `location_code`, and a tenant with no location at all answers 400 on its first receipt. The platform already runs this on `app.installed`, so calling it by hand is the repair for an install that predates the event or a `main` somebody deleted. Idempotent by CODE, not by contents: a location already carrying that code is reported under `existing` and is NOT touched, so a renamed or disabled `main` stays renamed and disabled. It creates nothing else and never removes a location.
      *
@@ -337,39 +355,39 @@ declare class InventoriesLocations {
      *
      * @param {string} params.id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      */
     inventoriesLocationsDelete(params: {
         id: string;
-    }): Promise<Models.Error>;
+    }): Promise<{}>;
     /**
      * Deleting one takes every `stock_levels` row that points at it with it — the foreign key decides that, not this route. What the database does NOT clean up is everything else carrying the same id: `stock_movements.location_id` and `reservations.location_id` are plain uuid columns and not foreign keys, so those rows stay exactly where they are, pointing at a row that no longer exists, and nothing nulls the pointer. That asymmetry destroys the balances and keeps everything that refers to them, so the route REFUSES while anything still depends on the location and answers 409 with the count — taken here rather than left to whoever is about to click delete, because a client that pre-counts asks a second question whose answer disagrees the moment a receipt lands between the two calls. Two things block it. A stock row still carrying `on_hand`: the cascade would destroy recorded inventory and nothing in this app ever replays the ledger to rebuild a balance, so there is no undo. And a reservation still `active`: a promise to a customer must not outlive the row backing it — such a hold used to survive its stock row, after which /release lowered no `reserved` and still wrote its `release` booking, and /commit booked the whole quantity as a shortfall, neither of them an error. A stock row at zero does not block: it records no quantity. HISTORY never blocks, and is never deleted either — a movement is an accounting record and removing one would falsify it, so the bookings stay, naming a location that no longer resolves, BY DESIGN. A location that once had traffic and now holds nothing is exactly what a merchant closes. To get past the 409, adjust the stock to zero and release or commit the holds; where the location is merely out of service, PUT `enabled: false` keeps every row and can be undone.
      *
      * @param {string} id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<{}>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsDelete(id: string): Promise<Models.Error>;
+    inventoriesLocationsDelete(id: string): Promise<{}>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the route that turns an id back into a place: `location_id` is on every stock row, every ledger booking and every reservation, and none of them carries the code or the name. Reading it also answers the two questions those rows raise — whether the location is still `enabled` (a disabled one is skipped by availability and reserve while its stock stays exactly where it is) and where its `priority` puts it when the allocation strategy picks somewhere to reserve from.
      *
      * @param {string} params.id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsGet(params: {
         id: string;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * A location is WHERE stock is kept — a warehouse, a shop floor, a supplier that dropships, or a virtual bucket for pre-orders and quarantine. It holds no quantity of its own: what is at it is a stock level. `type` is descriptive and nothing branches on it; `priority` is the number that decides which location a reservation is served from, and `enabled` decides whether it is offered at all. This is the route that turns an id back into a place: `location_id` is on every stock row, every ledger booking and every reservation, and none of them carries the code or the name. Reading it also answers the two questions those rows raise — whether the location is still `enabled` (a disabled one is skipped by availability and reserve while its stock stays exactly where it is) and where its `priority` puts it when the allocation strategy picks somewhere to reserve from.
      *
      * @param {string} id - The location.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsGet(id: string): Promise<Models.Error>;
+    inventoriesLocationsGet(id: string): Promise<Models.Location>;
     /**
      * Partial update: send the fields that change. The one with consequences is `enabled` — setting it to false is how a location is taken out of service WITHOUT losing anything. Availability and reserve stop looking at it, so its stock stops being sellable, while every stock row, ledger booking and reservation that points at it survives untouched and comes back the moment it is enabled again. That is the reversible alternative to DELETE, which is not reversible at all. Changing `code` is the other sharp edge: rows keep their `location_id` so nothing moves, but every caller that names the old code in `location_code` starts getting 400 "unknown location". Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert.
      *
@@ -383,7 +401,7 @@ declare class InventoriesLocations {
      * @param {number} params.priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} params.type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      */
     inventoriesLocationsUpdate(params: {
         id: string;
@@ -395,7 +413,7 @@ declare class InventoriesLocations {
         name?: string;
         priority?: number;
         type?: LocationType;
-    }): Promise<Models.Error>;
+    }): Promise<Models.Location>;
     /**
      * Partial update: send the fields that change. The one with consequences is `enabled` — setting it to false is how a location is taken out of service WITHOUT losing anything. Availability and reserve stop looking at it, so its stock stops being sellable, while every stock row, ledger booking and reservation that points at it survives untouched and comes back the moment it is enabled again. That is the reversible alternative to DELETE, which is not reversible at all. Changing `code` is the other sharp edge: rows keep their `location_id` so nothing moves, but every caller that names the old code in `location_code` starts getting 400 "unknown location". Two rows of this tenant may not share `code` — that is the 409, and it answers an update that moves a row onto a sibling's value exactly as it answers a second insert.
      *
@@ -409,10 +427,10 @@ declare class InventoriesLocations {
      * @param {number} priority - Sourcing order for POST /inventories/reserve while `allocation_strategy` is 'priority': the enabled locations are walked ASCENDING and the first that can cover the item wins, so a LOWER number is preferred. Locations that tie keep the order the database returns them in — give every location a distinct priority if the order matters. Defaults to 0.
      * @param {LocationType} type - What kind of place holds the stock. 'warehouse' — own stock, the default. 'store' — a retail floor, the stock a click-and-collect order draws on. 'dropship' — a supplier ships it and this row tracks what they say they hold. 'virtual' — a bucket that is not a building (pre-orders, consignment, a quarantine shelf). Descriptive only: sourcing order comes from `priority`, and no route in this app treats one type differently from another. Defaults to 'warehouse'.
      * @throws {RevenexxException}
-     * @returns {Promise<Models.Error>}
+     * @returns {Promise<Models.Location>}
      * @deprecated Use the object parameter style method for a better developer experience.
      */
-    inventoriesLocationsUpdate(id: string, address?: object, code?: string, enabled?: boolean, labels?: object, metadata?: object, name?: string, priority?: number, type?: LocationType): Promise<Models.Error>;
+    inventoriesLocationsUpdate(id: string, address?: object, code?: string, enabled?: boolean, labels?: object, metadata?: object, name?: string, priority?: number, type?: LocationType): Promise<Models.Location>;
 }
 
 export { InventoriesLocations };