@liquidcommerce/elements-sdk 2.6.0-beta.131 → 2.6.0-beta.132

package/dist/types/core/api/api-result.d.ts

@@ -2,6 +2,7 @@ export interface IApiErrorDetail {
     field?: string;
     message: string;
     code?: string;
+    retailerId?: string;
     fulfillmentId?: string;
 }
 export interface ApiError {

package/dist/types/modules/checkout/checkout.commands.d.ts

@@ -50,6 +50,9 @@ export declare class CheckoutCommands extends BaseCommand {
     private expiredDeliveryMarksWith;
     private pruneExpiredDeliveryWindows;
     private expireDeliveryWindows;
+    private requestPrepare;
+    private withStoreNamedFailure;
+    private knownRetailers;
     private prepareWithWindowRecovery;
     private prepareRecoveringWindow;
     retryLoadCheckout(): Promise<void>;

package/dist/types/utils/fulfillment-unavailable.d.ts

@@ -0,0 +1,8 @@
+import type { ApiError } from '@/core/api/api-result';
+export declare const FULFILLMENT_UNAVAILABLE_CODE = "fulfillment_unavailable";
+export interface FulfillmentRetailer {
+    id: string;
+    name: string;
+    fulfillments: Record<string, unknown>;
+}
+export declare function fulfillmentUnavailableMessage(error: Pick<ApiError, 'errors'> | null | undefined, retailers: FulfillmentRetailer[]): string | null;

package/docs/v1/api/actions/checkout-actions.md

@@ -480,6 +480,8 @@ If a saved window's cutoff passes, or the store's hours or zone rules no longer
 
 If prepare did not keep the window that was sent (error code `delivery_selection_not_accepted`, HTTP 409), the SDK drops the window it holds for that fulfillment so no later update sends it again. `chooseDeliverySlot` rejects with "We couldn't save that delivery time. Choose a delivery time again."; on any other update the window is recovered as an unavailable one.
 
+If a store cannot fulfill the selected delivery method at all, pickup included (error code `fulfillment_unavailable`, for example a closed store that offers no delivery window, or no estimate for the address), the SDK shows "W & J Wines & Spirits cannot fulfill this order now. Choose another store or delivery method." in place of the server's message, on loading the checkout, on any checkout update, on Place Order and on the cart's go-to-checkout. The store name comes from the cart or the checkout; when neither names the store, the message starts with "A store in your cart". The error detail carries the LC `retailerId` and `fulfillmentId` of each refused selection, so a custom UI can point at the store the same way. When AccelPay returns no estimates at all, Cloud refuses every selection, so the message names every store in the cart, even when the cause is the address.
+
 When scheduled delivery stops applying to the order (`delivery_scheduling_not_enabled`, `delivery_windows_unsupported` or `delivery_scheduling_unsupported`, and `multiple_fulfillment_groups` from an older server that schedules one group only), the SDK drops the saved window with a re-prepare, keeps the rest of checkout and shows "Scheduled delivery isn't available for this order right now. We'll deliver as soon as possible." The picker does not open; the response no longer carries `deliveryScheduling`, so the delivery time row goes away. Switching the delivery method never carries a window over to the new fulfillment.
 
 ## Use Cases

package/package.json

@@ -3,7 +3,7 @@
   "description": "LiquidCommerce Elements SDK",
   "license": "UNLICENSED",
   "author": "LiquidCommerce Team",
-  "version": "2.6.0-beta.131",
+  "version": "2.6.0-beta.132",
   "homepage": "https://docs.liquidcommerce.co/elements-sdk",
   "repository": {
     "type": "git",