@use-stall/types 0.4.0 → 0.6.0

package/index.d.ts

@@ -1,4 +1,5 @@
 export * from "./src/billing-payments";
+export * from "./src/catalog";
 export * from "./src/components";
 export * from "./src/customers";
 export * from "./src/device";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@use-stall/types",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Type declarations for Stall SDKs",
   "types": "index.d.ts",
   "type": "module",

package/src/catalog.d.ts

@@ -0,0 +1,57 @@
+import {
+  UnifiedAttributeType,
+  UnifiedVariantsAttributeType,
+} from "./product";
+
+/**
+ * The sellable projection of a product variant — a product/variant/inventory join, already
+ * scoped to one location and one sales channel. Computed server-side (stall-database) so
+ * every consumer (Terminal, any other channel) gets the same answer for "what can I sell,
+ * at what price, and how much is there" without doing any of that joining itself.
+ */
+export interface UnifiedCatalogVariantType {
+  id: string; // variant id
+  title: string;
+  description: string;
+  thumbnail: string;
+  sku: string;
+  barcode: string;
+  price: number;
+  sale_price: number;
+  price_currency: string;
+  on_sale: boolean;
+  default: boolean;
+  attributes: UnifiedVariantsAttributeType[]; // this variant's selected options, e.g. [{ name: "Size", option: "M" }]
+  inventory: {
+    unavailable: number; // at this location
+    committed: number; // at this location
+    in_stock: number; // at this location — available for new orders
+    on_hand: number; // at this location
+  };
+}
+
+/**
+ * A sellable product — the entity Terminal (and any other selling channel) should fetch
+ * instead of raw products. Only published products/variants that are assigned to the
+ * requested location and sales channel are ever included; nothing here needs client-side
+ * filtering or computation.
+ */
+export interface UnifiedCatalogType {
+  id: string; // product id
+  title: string;
+  handle: string;
+  description: string;
+  body_html: string;
+  thumbnail: string;
+  images: string[];
+  tax_class: string;
+  taxable: boolean;
+  categories: string[];
+  collections: string[];
+  brand: string;
+  tags: string[];
+  track_inventory: boolean; // from this product's default (or first) sellable variant
+  attributes: UnifiedAttributeType[]; // the axes of variation, e.g. [{ name: "Size", options: ["S","M","L"] }]
+  variants: CatalogVariantType[]; // already filtered to this location + sales channel
+  stock: number; // combined in_stock across variants, at this location
+}

package/src/fulfillment.d.ts

@@ -36,6 +36,21 @@ export interface UnifiedFulfillmentProviderConfigType {
   updated_at: string;
 }
 
+// The fulfillment-method counterpart to FrontendPaymentMethodType — same shape, minus
+// supported_currencies (fulfillment methods aren't currency-scoped like payment methods are).
+export interface FrontendFulfillmentMethodType {
+  id: string;
+  // Absent for methods with no fulfillment gateway to resolve, e.g. in-house pickup.
+  provider?: {
+    id: string; // provider id
+    name: string;
+    logo: string;
+  };
+  external_id: string;
+  name: string;
+  type: UnifiedFulfillmentMethods;
+}
+
 export type UnifiedFulfillmentStatus =
   | "pending"
   | "packing"

package/src/payments.d.ts

@@ -79,6 +79,8 @@ export interface FrontendPaymentMethodType {
   name: string;
   type: UnifiedMethodsType;
   supported_currencies: string[];
+  offline_support: boolean;
+  instant_clear: boolean; // whether the payment is cleared instantly like cash or custom
 }
 
 export type UnifiedPaymentCollectionStatus =