8b:T196d,# Vendure plugin to fulfill orders via QLS Vendure plugin to fulfill orders via QLS. This uses QLS as fulfillment center and does not support shipments only via QLS. This plugin contains: ## Product Sync - Full product sync (via Admin UI): - Fetches all products from QLS - Ensures corresponding Vendure variants exist - Updates Vendure stock levels from QLS - Partial product sync: Creates/updates products in QLS when products change in Vendure - Partial stock sync: Updates Vendure stock based on incoming QLS webhooks ## Additional EANs Additional EANs (or barcodes) are not automatically synced from Vendure to QLS. They can only be added manually via the `addAdditionalEANSToQLS` admin mutation. This mutation only adds EANs that do not already exist in QLS; existing EANs are skipped. Removal of additional EANs is not supported by this plugin and must be done inside the QLS platform itself. QLS may have assigned stock to those barcodes, so removing them should be handled in QLS directly. ```graphql mutation AddAdditionalEANSToQLS($variantId: ID!, $additionalEANS: [String!]!) { addAdditionalEANSToQLS(variantId: $variantId, additionalEANS: $additionalEANS) } ``` The mutation returns the list of all existing EANs for the product in QLS after the operation. The variant must already have a `qlsProductId` stored in its custom fields (i.e. it must have been synced to QLS first), otherwise an error is thrown. After adding EANs, the mutation also triggers a sync of the variant to QLS to ensure product fields are up to date. ## Order Sync - Pushes orders to QLS automatically on order placement - Supports manual order push to QLS via Admin UI - Updates order status in Vendure based on QLS webhooks ## Getting started ```ts import { QlsPlugin } from '@pinelab/vendure-plugin-qls-fulfillment'; // In your VendureConfig: plugins: [ QlsPlugin.init({ getConfig: (ctx) => { // Return config for the current channel, or undefined to disable QLS for this channel return { username: 'qls-username', password: 'qls-password', companyId: 'your-company-id', brandId: 'your-brand-id', }; }, webhookSecret: 'your-random-secret', productSync: { // Required: map Vendure variants to QLS product fields getAdditionalVariantFields: (ctx, variant) => ({ ean: variant.sku, image_url: `https://your-cdn.com/${variant.featuredAsset?.preview}`, }), // Optional: exclude certain variants from being synced to QLS excludeVariantFromSync: (ctx, injector, variant) => { return variant.sku.startsWith('DONOTSYNC'); }, }, orderSync: { // Optional: push additional fields to QLS when creating an order pushAdditionalOrderFields: (ctx, injector, order) => ({ custom_values: [ { key: 'vendureOrder', value: `https://your-admin.com/admin/orders/${order.code}`, }, ], }), // Optional: delay order processing in QLS by 2 hours processOrderFrom: (ctx, order) => { return new Date(Date.now() + 1000 * 60 * 60 * 2); }, }, }), ]; ``` This plugin requires the default order process to be configured with `checkFulfillmentStates: false`, so that orders can be transitioned to Shipped and Delivered without the need of fulfillment. Fulfillment is the responsibility of Picqer, so we won't handle that in Vendure when using this plugin. ## Webhooks You should set up webhooks for the following events: - `fulfillment_order.cancelled` - `fulfillment_product.stock` - `fulfillment_order.status` - `fulfillment_order.completed` The URL for all these events should be `https:///qls/webhook/?secret=`. E.g. `https://example.com/qls/webhook/your-channel-token?secret=121231`. - `` is the URL of your Vendure instance. - `` is the token of the channel you want to use. - `` is the webhook secret you've passed into the plugin's `init()` function. ### Stock location setup This plugin only uses Vendure's default stock location, that means you should either: 1. Remove all but one stock location in Vendure 2. Or, remove all stock from other stock locations than the default in Vendure Vendure assumes the first created stock location is the default stock location. ## Service Points You can use the query `qlsServicePoints(postalCode: String!): [QlsServicePoint!]!` to get the service points for a given postal code. You can use the `setOrderCustomFields` mutation to set the service point on an order. ```graphql mutation { setOrderCustomFields( input: { customFields: { qlsServicePointId: "12232" # This is the ID of one of the points returned by the query above qlsServicePointDetails: "Some details about the service point for admin users" # This is just for admin users in Vendure } } ) { __typename ... on Order { id code customFields { qlsServicePointId qlsServicePointDetails } } } } ``` ## Monitoring failed orders and product syncs Whenever an order fails to be pushed to QLS, an event is emitted. You can listen to this event to monitor failed orders. ```ts this.eventBus.ofType(QlsOrderFailedEvent).subscribe((event) => { console.log('Order failed to be pushed to QLS:', event.order.code); }); ``` Because a job can be retried, this event can be emitted multiple times for the same order. You can use the date field together with the order code to determine if you have already processed this event. ```ts this.eventBus.ofType(QlsOrderFailedEvent).subscribe((event) => { // Determine if we have already processed this event. const uniqueEventId = `${event.order.code}_${ event.failedAt.toISOString().split('T')[0] }`; // "JHD82JS8868_2026-01-01" console.log('Order failed to be pushed to QLS:', event.order.code); }); ``` For product syncs, the same approach can be used, but with the `QlsProductSyncFailedEvent` instead. ## Manually pushing orders to QLS This plugin adds a button `push to QLS` to the order detail page in the Admin UI. This will push the order to QLS again. If the order has been pushed before, you need to uncheck the checkbox `synced to QLS` in the order custom fields first. Pushing an order to QLS again will not cancel the existing order in QLS. Cancel existing orders first via https://mijn.pakketdienstqls.nl/. 8c:T1258,# 3.2.0 (2026-08-12) - Restore the legacy Angular Admin UI extension alongside the React Dashboard. # 3.1.0 (2026-08-12) - Trigger `saveAdditionalVariantData` from incoming stock webhooks using the webhook payload directly. - Avoid fetching the QLS product entity during this flow. - Add webhook coverage for additional variant data. # 3.0.0 (2026-07-29) - Migrated to React Dashboard. - Added React Dashboard action bar items for product sync, order link, push order, variant link, and adding additional EANs. - Kept legacy Angular Admin UI action bar items for backward compatibility. - Corrected the UI permission for the "Push order to QLS" action to `QLSPushOrder`. # 2.3.0 (2026-08-05) - Extra prompt before adding an additional EAN # 2.2.1 (2026-07-15) - Emit `StockMovementEvent` with corresponding `StockAdjustment` whenever a QLS webhook updates stock of a variant. # 2.2.0 (2026-07-15) - Added buttons on variant and order detail to view the product and order in QLS dashboard. # 2.1.0 (2026-07-08) - Added `addAdditionalEANSToQLS` admin mutation to manually add additional EANs/barcodes to existing QLS products. - Added admin UI action on the product variant detail page to prompt for and add a single additional EAN. - Removed automatic syncing of additional EANs during product sync; EANs must now be added manually via the mutation. - Removed obsolete `util.ts`, `util.spec.ts`, and `removeBarcode` QLS client method. # 2.0.2 (2026-07-01) - Verify barcode deletion in QLS by fetching remaining barcodes after removal attempt - Emit `QlsVariantSyncFailedEvent` and log an error when barcodes fail to be removed from QLS # 2.0.1 (2026-06-15) - Fixed fulfillment product detail type # 2.0.0 (2026-06-10) - Restructure plugin options into nested `orderSync` and `productSync` objects. This is a **breaking change**: all plugin options must now be organized under `orderSync` (for order-related hooks) and `productSync` (for product-related hooks). - Renamed `getAdditionalOrderFields` to `pushAdditionalOrderFields` in `orderSync` options. - Added `pullAdditionalOrderFields` hook in `orderSync` options, called after an order is successfully created in QLS. Errors in this hook are caught and logged, and will not fail the order push job. # 1.9.0 (2026-08-05) - Upgraded to Vendure 3.6.3 # 1.8.2 (2026-04-24) - Added `variant` parameter to the `saveAdditionalData` hook # 1.8.1 (2026-04-24) - Replaced `saveRawWarehouseStockData` boolean with `saveAdditionalData` hook, allowing you to handle and persist any QLS product data yourself # 1.8.0 (2026-04-21) - Added configurable `saveRawWarehouseStockData` option # 1.7.0 (2026-03-15) - Pass order phone number to QLS # 1.6.0 (2026-03-09) - Skip syncing disabled products/variants to QLS # 1.5.1 (2026-02-18) - Pass error message to `QlsVariantSyncFailedEvent` instead of the error object. # 1.5.0 (2026-02-18) - Allow passing additional order items with `addAdditionalOrderItems()` that will be added to the QLS order. # 1.4.0 (2026-02-11) - Allow `qlsProductIdUiTab` to be `null` to show QLS Product ID on the default Admin UI tab. - Map QLS order status: `sent` → Delivered, `partically_sent` → PartiallyDelivered. # 1.3.0 (2026-02-05) - Upgraded to Vendure 3.5.3 # 1.2.1 (2026-01-28) - Use 'varchar' instead of 'text' for QLS order id and Vendure order id in database. # 1.2.0 (2026-01-28) - Prevent accidently pushing orders multiple times by checking if the order is already synced to QLS. - Store combination of QLS order id and Vendure order id to prevent duplicate orders in QLS. - Emit event for failed product pushes, and log it as a warning instead of an error. - Store failed products as scheduled task data so they can be viewed in the Admin UI. - Allow specifying UI tab name where the QLS product ID custom field is shown on ProductVariant page. # 1.1.3 (2026-01-28) - Gracefully handle missing variants from incoming webhooks by logging instead of throwing an error. # 1.1.2 (2026-01-14) - Run scheduled full sync without job queue, because scheduled tasks already run in the worker only. - Export scheduled task instead of automatically adding it to the config. # 1.1.1 (2026-01-07) - Ignoring non-existing order codes in order status updates, instead of throwing an error. - Update `syncedToQls` custom field inside same transaction, to prevent `Query runner already released. Cannot run queries anymore` errors. # 1.1.0 (2026-01-07) - Fix delivery options to be an array of objects with a tag property - Emit event for failed order push - Delay 10s before setting custom field `syncedToQls` to prevent race conditions. # 1.0.0 (2025-11-07) - Initial release 8d:T644,# Vendure Limited Products Plugin This plugin allows you to: 1. Limit the amount of a specific product per order. I.E. A customer is only allowed to buy 1 of product "Limited art t-shirt X" per order. 2. Only allow a product to be purchased in multiples of X. E.g. only per 4 items. ## Getting started 1. Add the following config to your `vendure-config.ts`: ```ts import { LimitedProductsPlugin } from '@pinelab/vendure-plugin-limited-products'; plugins: [LimitedProductsPlugin]; ``` The custom field input for `Maximum amount per order` and `Multiple of per order` is provided as a React Dashboard extension — no Admin UI compilation step is needed. 2. Run a database migration to add the custom fields. 3. Start Vendure, login and go to the product you want to limit. 4. Set the custom field `Maximum amount per order` and `Multiple of per order` on a variant and update the product 5. Customers can now only buy X amount of the variant per order. The same customer can still order the product again in a new order. You can fetch `product.limitPurchasePerMultipleOf` and `product.maxQuantityPerOrder` via the Shop API to display messages on your storefront accordingly. ## Migrating to V3.x V3 removes the fields from the variant and places them on a Product, in a different format. This plugin isn't used much, so there is no migration script available. We do it manually: 1. Back up all values of the variants before installing the plugin. 2. Install V4 of this plugin, and run a database migration. 3. Start the server and set the values on the parent products via the Admin UI 8e:T464,# 3.5.1 (2026-08-04) - Include dashboard extensions in dist. # 3.5.0 (2026-07-21) - Migrated to React Dashboard # 3.4.0 (2026-08-05) - Upgraded to Vendure 3.6.3 # 3.3.0 (2026-02-05) - Upgraded to Vendure 3.5.3 # 3.2.2 (2025-11-13) - Documentation update # 3.2.1 (2025-11-06) - Updated official documentation URL # 3.2.0 (2025-06-04) - Upgrade to Vendure to 3.3.2 # 3.1.0 (2024-12-19) - Update Vendure to 3.1.1 # 3.0.1 (2024-08-04) - Update compatibility range (#480) # 3.0.0 (2024-07-30) - Refactored this plugin to 'Limited Products' - Moved the limitation custom fields to the product level instead of variant - Made maxPerOrder also channel aware # 2.2.0 (2024-07-25) - Moved custom fields to their own tab 'Limitations' # 2.1.1 (2024-06-21) - Bugfix related to unable to add items: #470 # 2.1.0 (2024-06-21) - Updated Vendure to 2.2.6 # 2.0.0 (2024-04-10) - Added support for channel aware `onlyAllowPer` value per ProductVariant # 1.2.0 (2024-03-08) - Added support for adding a multiple of `onlyAllowPer` of a `ProductVariant` per `Order` # 1.1.0 (2023-10-24) - Updated vendure to 2.1.1 8f:T137e,# Vendure Drop Off Points Plugin Show nearby parcel drop off points to your customers. Supports multiple carriers and allows custom carriers. Also known as collection points or pickup points. ## Getting started Add the plugin to your `vendure-config.ts`: ```ts // vendure-config import { DropOffPointsPlugin, DHLCarrier, } from '@pinelab/vendure-plugin-drop-off-points'; plugins: [ DropOffPointsPlugin.init({ carriers: [ new DHLCarrier(), // You can add more custom carriers here ], }), ]; ``` Run a database migration to add the drop off point custom fields to an order. If you want to use your own custom fields, see "Using your own custom fields" below. ## Storefront usage 1. Fetch nearby drop off points: ```graphql query { parcelDropOffPoints( input: { carrier: "DHL", postalCode: "8932BR", houseNumber: "48" } ) { token dropOffPointId name streetLine1 streetLine2 postalCode houseNumber houseNumberSuffix city country latitude longitude distanceInKm cutOffTime additionalData } } ``` 2. Set the selected drop off point on the order: ```graphql mutation { setParcelDropOffPoint(token: ${selectedPoint.token} ) { id code customFields { dropOffPointCarrier dropOffPointId dropOffPointName dropOffPointStreetLine1 dropOffPointStreetLine2 dropOffPointHouseNumber dropOffPointHouseNumberSuffix dropOffPointPostalCode dropOffPointCity dropOffPointCountry } } } ``` If your customer decides to not use a drop off point, you should call `unsetParcelDropOffPoint` to void all the fields again. ## Using your own custom fields By default, this plugin creates the following custom fields on an order: `dropOffPointCarrier, dropOffPointId, dropOffPointName, dropOffPointStreetLine1, dropOffPointStreetLine2, dropOffPointHouseNumber, dropOffPointHouseNumberSuffix, dropOffPointPostalCode, dropOffPointCity, dropOffPointCountry`. If you would like to use your own custom fields for drop off points, you can implement the `setDropOffPointOnOrder` and `unsetDropOffPoint` functions, like so: ```ts // vendure-config.ts DropOffPointsPlugin.init({ carriers: [new DHLCarrier()], // Use your own custom fields here customMutations: { setDropOffPointOnOrder: (ctx, order, dropOffPoint) => { order.customFields.pickupPointName = dropOffPoint.name; // Other fields go here return order; }, unsetDropOffPoint: (ctx, order) => { order.customFields.pickupPointName = null; // Other fields go here return order; } } }), ``` If you supply `customMutations` in the plugin config, you don't have to do a database migration, because the plugin will not add any custom fields to the order. ## Custom carriers You can easily implement your own drop off point carriers, by implementing the `DropOffPointCarrier` interface. ```ts // my-custom-carrier.ts import { RequestContext } from '@vendure/core'; import { DropOffPoint, DropOffPointCarrier, ParcelDropOffPointSearchInput, } from '@pinelab/vendure-plugin-drop-off-points'; export class CustomCarrier implements DropOffPointCarrier { readonly name = 'CustomCarrier'; async getDropOffPoints( ctx: RequestContext, input: ParcelDropOffPointSearchInput ): Promise { let url = `https://my-carrier-api.com/pickup-points=postalcode=${input.postalCode}`; if (input.houseNumber) { url += `&houseNumber=${input.houseNumber}`; } const response = await fetch(url); if (!response.ok) { throw new Error( `Failed to fetch drop-off points: [${response.status}] ${response.statusText}` ); } const points = (await response.json()) as any; return points.map((point) => ({ dropOffPointId: point.id, name: point.name, houseNumber: point.address.number, houseNumberSuffix: point.address.addition, streetLine1: point.address.street, streetLine2: undefined, postalCode: point.address.postalCode, city: point.address.city, country: point.address.countryCode, cutOffTime: point.collectionSchedule.time, latitude: point.geoLocation.latitude, longitude: point.geoLocation.longitude, distanceInKm: point.distance, })); } } ``` You can then pass it into the plugin: ```ts // vendure-config plugins: [ DropOffPointsPlugin.init({ carriers: [new CustomCarrier()], }), ]; ``` ## Why are ID's/tokens so long? TL;DR: Avoid an extra API call to drop off point carrier. The drop off point's `token` is a base64 encoded string of the address details of a point. This is used to save the drop off point on an order when you call the `setParcelDropOffPoint` mutation, without the need to refetch the points from the external API. 90:Tc53,# Vendure MyParcel Plugin Plugin for sending placed orders to MyParcel. ## Getting started 1. Add this to your plugins in `vendure-config.ts`: ```ts import { MyparcelPlugin } from '@pinelab/vendure-plugin-myparcel'; plugins: [ MyparcelPlugin.init({ vendureHost: 'https://your-vendure-host.io', syncWebhookOnStartup: true, // If you want to automatically set vendureHost as webhook on MyParcel account }), ... ] ``` 2. Start Vendure and go to `Settings` > `Channels`, open the channel you want to configure and select the **MyParcel** tab. Tick `Enabled` and fill in your MyParcel `API key`. Configuration is stored per channel as Channel custom fields, so no Admin UI extension needs to be compiled. 3. Create a shipmentMethod with `MyParcel fulfillment`. 4. Place an order and select the shippingMethod. 5. Go to the Admin UI and click on `fulfill` 6. Your shipment should be in your MyParcel account. > The `myparcelEnabled` toggle controls whether MyParcel is active for a channel. > When it is off (or no API key is set), the plugin is disabled for that channel. ## Customs information for shipments outside the EU MyParcel requires additional customs information for shipments outside the EU. When you ship outside the EU, you should implement the `getCustomsInformationFn` when initializing the plugin: ```ts MyparcelPlugin.init({ vendureHost: 'https://your-vendure-host.io', getCustomsInformationFn: (orderItem) => { return { weightInGrams: (orderItem.line.productVariant.product.customFields as any) .weight, classification: ( orderItem.line.productVariant.product.customFields as any ).hsCode, countryCodeOfOrigin: 'NL', }; }, }); ``` You can find more information about the classification codes [here](https://myparcelnl.github.io/api/#7_E). ## Custom shipment strategy If you want more control over the data that is send over to MyParcel, then you can implement a custom `shipmentStrategy`. The shipment strategy needs to implement `MyParcelShipmentStrategy` and should containt the `getShipment` method. This method returns the shipment object for MyParcel [API reference](https://developer.myparcel.nl/api-reference/06.shipments.html) If you only need to change the recipient or the options, you can extend the `MyParcalDefaultShipmentStrategy` and overwrite the method you need. - `getOptions` - `getRecipient` ```ts class CustomShipmentStrategy extends MyParcalDefaultShipmentStrategy { getShipment(address: OrderAddress, order: Order, customsContent: string) { const shipment: MyparcelShipment = { carrier: 2, //bpost. Only available on sendmyparcel.be reference_identifier: order.code, options: this.getOptions(address, order, customsContent), recipient: this.getRecipient(address, order, customsContent), }; return shipment; } } ``` Pass you strategy to the MyparcelPlugin config. ```ts MyparcelPlugin.init({ vendureHost: 'https://your-vendure-host.io', shipmentStrategy: new CustomShipmentStrategy(), }); ``` `getCustomsInformationFn` will still be processed after the custom shipment strategy 91:Tad4,# Vendure Validate Cart Plugin A very lightweight plugin to have custom cart validation rules before proceeding to checkout. For example to check current stock, or check for limited products. You can implement your own validation rules by implementing the `CartValidatorStrategy` interface. ## Getting started Add the plugin to your config: ```ts import { ValidateCartPlugin, DefaultStockValidationStrategy, } from '@pinelab/vendure-plugin-validate-cart'; // In your plugins array, in vendure-config.ts plugins: [ ValidateCartPlugin.init({ // This is just the sample strategy that checks if the cart has enough stock for the items in the cart. validationStrategy: new DefaultStockValidationStrategy(), }), ]; ``` This will add a `validateActiveOrder` mutation to the shop API. ## Storefront usage Depending on your validation strategy, you probably want to call the `validateActiveOrder` mutation in the cart page, and again on the payment page: ```gql mutation ValidateActiveOrderMutation { validateActiveOrder { errors { message errorCode relatedOrderLineIds } order { id lines { productVariant { product { id } } } } } } ``` If any validation errors are returned, you can display the error to the user with the corresponding order lines. You could even automatically remove the items from the cart based on the `relatedOrderLineIds`. The `order` field returns the active order after validation, including any modifications made by a custom validation strategy. This action is a mutation rather than a query, because your custom validation logic might need to modify the order, for example to 'lock' an order after validation until payment is completed. ## Custom validation rules You can implement your own validation rules by implementing the `CartValidatorStrategy` interface. For example, to check if active promotions are still valid for the items in the cart. ```ts import { ValidateCartStrategy, ActiveOrderValidationError, } from '@pinelab/vendure-plugin-validate-cart'; export class PromotionValidator implements ValidateCartStrategy { // Tell the plugin to pre-load the promotions for the order loadOrderRelations: RelationPaths = ['promotions']; // Validate the order based on your custom logic async validate(ctx: RequestContext, activeOrder: Order, injector: Injector) { const errors: ActiveOrderValidationError[] = []; for (const promotion of activeOrder.promotions) { if (!isPromotionValid(promotion)) { errors.push({ message: `Promotion ${promotion.name} is not valid`, errorCode: `INVALID_PROMOTION`, }); } } return errors; } } ``` 92:T49e,# 1.3.1 (2026-07-01) - Fixed error `The property totalQuantity on the Order entity requires the Order.lines relation to be joined` when querying calculated Order fields (e.g. `totalQuantity`, `total`, `totalWithTax`, `subTotal`) on the `validateActiveOrder` result. The `lines` relation is now always joined when refetching the order. # 1.3.0 (2026-07-01) - `validateActiveOrder` now returns a `ValidateActiveOrderResult` object with both `errors` and `order` fields. - The active order is refetched after validation, so any modifications made by a custom validation strategy are reflected in the returned order. - Uses Vendure's built-in `@Relations` decorator to load the requested order relations in the response. - **Breaking change:** The `validateActiveOrder` mutation return type changed from `[ActiveOrderValidationError!]!` to `ValidateActiveOrderResult!`. # 1.2.0 (2026-08-05) - Upgraded to Vendure 3.6.3 # 1.1.0 (2026-02-05) - Upgraded to Vendure 3.5.3 # 1.0.3 (2025-11-13) - Documentation update # 1.0.2 (2025-11-06) - Updated official documentation URL # 1.0.1 (2025-10-28) - Fixed type declaration in package.json # 1.0.0 (2025-09-24) - Initial release 93:T1cae,# Vendure Store Credit Plugin A plugin for channel-aware store credit wallets with ledger tracking. Customers can use wallet balance as a payment method at checkout. ![Store Credit Wallets](https://plugins.pinelab.studio/plugin-images/store-credit-wallets.png) ## Installation ```bash npm i @pinelab/vendure-plugin-store-credit ``` ```ts // vendure-config.ts import { StoreCreditPlugin } from '@pinelab/vendure-plugin-store-credit'; plugins: [StoreCreditPlugin], ``` Run a migration to add the Wallet entities to the database, then create a Payment Method in the admin using the `store-credit` handler. You also need to rebuild the admin dashboard to see the new Store Credit Wallets on the customer detail page. ## Admin API These functions are available in the admin API. ### Create wallet Each customer can have multiple wallets. This mutation creates a new wallet for the customer. Starting balance is always 0. ```graphql mutation CreateWallet($input: CreateWalletInput!) { createWallet(input: $input) { id name balance currencyCode adjustments { id amount } } } # Variables: { "input": { "customerId": "1", "name": "Gift card" } } ``` ### Set balance (add or subtract) ```graphql mutation AdjustBalance($input: AdjustBalanceForWalletInput!) { adjustBalanceForWallet(input: $input) { id balance } } # Variables: { "input": { "walletId": "1", "amount": 1500 } } # Amount in minor units (1500 = €15.00). Use negative for deductions. ``` ### Refund payment to store credit An admin can choose to refund any payment to store credit wiht the custom `refundPaymentToStoreCredit` mutation: ```graphql mutation RefundToStoreCredit($paymentId: ID!, $walletId: ID!) { refundPaymentToStoreCredit(paymentId: $paymentId, walletId: $walletId) { id balance } } ``` To refund a payment that was made with store credit, you can use the built-in `refundOrder` mutation supplied by Vendure. In this case it will refund the store credit to the same wallet that was used to make the payment. ## Storefront usage Customers can pay for orders using their store credit balance. ```graphql mutation { addPaymentToOrder( input: { method: "store-credit", metadata: { walletId: "1" } } ) { ... on Order { id code } } } ``` Optionally, a customer can choose to partially pay for an order by specifying the amount to pay with store credit. ```graphql mutation { addPaymentToOrder( input: { method: "store-credit" metadata: { walletId: "1", amount: 100000 } } ) { ... on Order { id code } } } ``` Logged-in customers can fetch their wallets via `activeCustomer`: ```graphql query MyWallets { activeCustomer { id wallets { items { id name balance currencyCode adjustments { amount } } totalItems } } } ``` Or query a single wallet by ID: ```graphql query Wallet($id: ID!) { wallet(id: $id) { id name balance currencyCode adjustments { id amount createdAt } } } ``` ## Gift cards You can configure the plugin to automatically create gift card wallets when certain products are ordered. Use the `createGiftCardWallet` hook in the plugin options: ```ts StoreCreditPlugin.init({ createGiftCardWallet: async (ctx, injector, order, orderLine) => { // Return { price, cardCode } to create a gift card wallet for this item // Returning false skips this item }, }); ``` The hook is called **once for each quantity per order line item**. For example, if an order has 1 order line with a giftcard, and the quantity is 3, the hook is invoked 3 times, allowing you to return a different `cardCode` for each individual gift card. The generated gift card codes are saved to the order line's `giftCardCodes` custom field, so you can reference them later (e.g. for email delivery or customer notifications). ### Paying with a gift card code Customers can pay for an order by providing the gift card code at checkout. The full wallet balance will be applied to the order (up to the outstanding amount). ```graphql mutation { addPaymentToOrder( input: { method: "store-credit", metadata: { giftCardCode: "ABC123" } } ) { ... on Order { id code } } } ``` To only pay a specific amount with the gift card, include the `amount` in the metadata: ```graphql mutation { addPaymentToOrder( input: { method: "store-credit" metadata: { giftCardCode: "ABC123", amount: 100000 } } ) { ... on Order { id code } } } ``` ## Gift card code security Gift card wallets are identified by their `code`. Treat this code like cash: anyone who knows the code can spend the wallet. It is the responsibility of the consuming project (via the `createGiftCardWallet` strategy) to make sure the returned `cardCode` is sufficiently unguessable — use a cryptographically secure random generator (e.g. `crypto.randomUUID()` or `generatePublicId()` from `@vendure/core`) and never derive the code from predictable data like order id or sequence numbers. The `walletByCode` query has a few safeguards to reduce enumeration risk: - on the admin API it requires the `UpdateOrder` permission; - on the shop API it requires the caller to have an active order on the session; - it returns `null` for unknown codes (instead of throwing) so the API does not leak whether a given code exists; - lookups are channel-scoped. # Helper scripts You can create wallets with a specified balance for all (or given) customers with the following script that is included: ```ts import { bootstrap } from '@vendure/core'; import { createWalletsForCustomers } from '@pinelab/vendure-plugin-store-credit'; import dotenv from 'dotenv'; dotenv.config({ path: process.env.ENV_FILE }); // Import vendure config after dotenv.config() so env variables are available in config import('./vendure-config') .then(async ({ config }) => { const app = await bootstrap(config); const wallets = await createWalletsForCustomers( app, // Details for all wallets { name: 'Special promotion wallet', balance: 123456, balanceDescription: 'Special promotion credits', }, // Administrator email address to use for record-keeping 'admin@example.com', // A list of customer email addresses to create wallets for. If omitted, all customers get a wallet. undefined ); console.log(`Created ${wallets.length} wallets`); await app.close(); }) .catch((err) => { console.error(err); }); ``` # FAQ ## Can I create a wallet with an initial starting balance? To create a wallet with an initial starting balance, you can create a wallet for a customer on the customer detail page in the admin dashboard. Wallets always start with a balance of 0, but you can adjust the balance to anything you want after creation. Wallets always start with 0, so that you can recalculate the current balance by 'rerunning' all the adjustments. ## Can I delete a customer's wallet? Currently you can not delete a wallet, because of accountability: you need to be able to see the history of adjustments on the wallet. Future version will allow you to archive a wallet. 94:Tbca,# 2.1.0 (2026-08-06) - Allow creating gift cards via the Dashboard. # 2.0.2 (2026-08-04) - Auto-created gift cards are no longer linked to the purchasing customer, so they can be used by any customer with the gift card code. - Made `WalletAdjustment.mutatedBy` optional, allowing gift-card payments to be recorded without an active user (e.g. anonymous/guest customers). - **BREAKING**: A database migration is required. Drop the `NOT NULL` constraint on `wallet_adjustment.mutatedById` so that adjustments can be created without an associated user. # 2.0.1 (2026-08-04) - Added documentation for paying with a gift card code, with and without a specified amount. # 2.0.0 (2026-07-21) - **BREAKING**: The `createGiftCardWallet` hook is now called once per order line quantity instead of once per order line. This allows returning different gift card configurations for each individual item when the quantity of an order line is > 1. - Added `giftCardCodes` custom field to `OrderLine` to store generated gift card codes. - Renamed `GiftCardWalletCreatedEvent` to `GiftCardsCreatedEvent`. The old class name is kept as a deprecated alias. - A database migration is required due to the new custom field. # 1.7.0 (2026-07-21) - Migrated to React Dashboard # 1.6.0 (2026-08-05) - Upgraded to Vendure 3.6.3 # 1.5.0 (2026-04-15) - Added support for `Wallet` based Gift Cards - Security: `walletByCode` is now channel-scoped, returns `null` for unknown codes, requires `UpdateOrder` on the admin API and an active order on the shop API (to prevent enumeration attacks) - Security: wallet debits are now performed atomically to prevent race conditions / double-spend - BREAKING: `WalletService.create` now throws when neither `customerId` nor `code` is provided. The admin `CreateWalletInput` has a new optional `code` field; pass a code explicitly when creating a wallet without a customer - BREAKING: the admin `giftCardWallets` query now requires the `ReadCustomer` permission - The removed unique index on `wallet.name` allows duplicate wallet names across customers # 1.4.1 (2026-02-20) - Include raw .tsx components for React Extension distribution # 1.4.0 (2026-02-13) - Add pagination support for querying adjustments on wallets. - BREAKING: `wallet.adjustments` is now paginated, that means you need to query `adjustments { items { ...fields } }` instead of `adjustments { ...fields }`; # 1.3.0 (2026-02-12) - Added metadata field on a wallet for custom data # 1.2.0 (2026-02-12) - Added dashboard components for managing wallets and balance on the customer detail page. - BREAKING: DB migration required, balance is now defined as `Money` to prevent rounding errors. # 1.1.0 (2026-02-03) - Accept amount as input to the store credit payment handler, to partially pay for an order with store credit - Export helper functions to populate wallets for customers - BREAKING: DB migration required: Customers can not have multiple wallets with the same name # 1.0.0 (2026-02-03) - Initial release 95:T9a5,# Vendure Google Sheet Loader plugin This plugin allows you to load data from a Google Sheet and handle the data in Vendure. For example, to load products and prices into Vendure. You can define a single action per channel. This means each channel can have it's own sheet, and it's own way of handling the data from that sheet. ## Getting started You need to have a Google API key to use this plugin. You can get one [here](https://support.google.com/googleapi/answer/6158862?hl=en). 1. Add this to your plugin in `vendure-config.ts`: ```ts import { GoogleSheetLoaderPlugin } from '@pinelab/vendure-plugin-google-sheet-loader'; plugins: [ GoogleSheetLoaderPlugin.init({ strategies: [new MyDataLoadingStrategy()], googleApiKey: 'test-api-key', }), ... ] ``` 2. The "Load Google Sheet data" action is added as a dropdown item in the product list page's action bar via the React Dashboard extension API — no Admin UI compilation step is needed. Before you can use this plugin, you need to implement your own data loading strategy. This strategy determines what will be done with the data from the sheet. ```ts import { RequestContext, Injector } from '@vendure/core'; import { GoogleSheetDataStrategy, SheetContent, } from '@pinelab/vendure-plugin-google-sheet-loader'; export class MyDataLoadingStrategy implements GoogleSheetDataStrategy { code = 'MyDataLoadingStrategy'; getSheetMetadata() { return { sheets: ['My tab'], spreadSheetId: '1gqZpM-Ksxc-xxKJAKNALAFNLLkksdalakml', }; } validateSheetData( ctx: RequestContext, sheets: SheetContent[] ): boolean | string { // Single sheet example const sheet = sheets[0]; const headerRow = sheet.data[0]; if (headerRow[0] !== 'My Header Column') { return 'Expected "My Header Column" for column 1'; } return true; } async handleSheetData( ctx: RequestContext, injector: Injector, sheets: SheetContent[] ): Promise { // Do whatever you want with the data here // This part is executed in the worker return `Successfully processed ${sheets[0].data.length} rows`; } } ``` ## How it works When the data loading is triggered from the product overview page in the admin UI, the plugin will: 1. Get the sheet metadata from the strategy 2. Fetch the content of the sheets 3. Validate the data, and give feedback to the admin user 4. If valid, a job will be created to handle the data 96:T849,# Vendure Anonymized Order This plugin enables the retrieval of an anonymized customer order. By default, the `anonymizedOrder` query omits the fields `customer`, `billingAddress`, and `shippingAddress` from the order details. However, users have the flexibility to further customize this process by adding a callback, allowing the removal of additional fields as needed. ## Getting started Add the plugin to your config: ```ts import { AnonymizedOrderPlugin } from '@pinelab/vendure-plugin-anonymized-order'; plugins: [AnonymizedOrderPlugin.init({})]; ``` ## Displaying placed order without requiring the customer to log in The `anonymizedOrder` query can be used to display a customers' placed order permanently, instead of for a limited time only, like the built-in `orderByCode` query. This can be used to show a placed order via a link in email for example. In the order confirmation email, you could have a link like `https://my-storefront.io/order/GX83VCD73?emailAddress=the-customer@email.com`. On your storefront, you'd then use the following query to display the order: ```graphql anonymizedOrder(orderCode: "GX83VCD73", emailAddress: "the-customer@email.com") { id code totalWithTax lines { id linePriceWithTax } } ``` This will then return the order without `shippingAddress`, `billingAddress` and `customer` fields. ## Customizing what data is removed You can supply your own strategy for anonymizing a given order. In that case, **the plugin will not remove any data from the order** for you. The example below will only remove the customer, but still expose shipping and billing address: ```ts import { AnonymizedOrderPlugin } from '@pinelab/vendure-plugin-anonymized-order'; plugins: [ AnonymizedOrderPlugin.init({ anonymizeOrderFn: (order) => { order.customer = {}; }, }), ]; ``` You should be cautious about what to return, because of the relational nature of GraphQL. For example, exposing the `order.customer`, will also allow the client to query `order.customer.orders`, thus exposing all orders of that customer. 97:T116a,# Vendure Address Lookup This Vendure plugin allows you to lookup addresses based on postalcode, housenumber and/or streetname. ## Getting started ```ts import { AddressLookupPlugin } from '@pinelab/vendure-plugin-address-lookup'; // In your vendure-config.ts plugins: [ AddressLookupPlugin.init({ lookupStrategies: [ // You can register for the Post NL API to do NL and BE lookups new PostNLLookupStrategy({ apiKey: process.env.POSTNL_APIKEY!, }), new GooglePlacesLookupStrategy({ supportedCountryCodes: ['DE'], // You can use the Google Places API for any country, but you need to register for an API key at https://developers.google.com/maps/documentation/places/web-service/get-api-key apiKey: process.env.GOOGLE_PLACES_APIKEY!, }) // If you want to use the free BAG API (NL only), get an API key at https://www.kadaster.nl/zakelijk/producten/adressen-en-gebouwen/bag-api-individuele-bevragingen and uncomment the lines below // new BAGLookupStrategy({ // apiKey: process.env.BAG_APIKEY!, // }), ], }), DefaultSearchPlugin, AdminUiPlugin.init({ port: 3002, route: 'admin', }), ], ``` ## Storefront usage In your storefront, you can use the `lookupAddress` mutation to look up an address. You need an active order to be able to access this query! ```gql # NL lookups with postal code and house number will always give 1 result query { lookupAddress( input: { countryCode: "NL", postalCode: "8911 DM", houseNumber: "3" } ) { streetLine1 streetLine2 postalCode city province country countryCode } } # BE lookups with only a postal code and a house number will give multiple results query { lookupAddress( input: { countryCode: "BE", postalCode: "9052", houseNumber: "110" } ) { streetLine1 streetLine2 postalCode city country countryCode } } # To get a single result, you need to also pass streetname query { lookupAddress( input: { countryCode: "BE" postalCode: "9052" houseNumber: "110" streetName: "Rijvisschepark" } ) { streetLine1 streetLine2 postalCode city country countryCode } } ``` ## Google Places Strategy If you want to use the Google Places API, you can do so by registering the `GooglePlacesLookupStrategy` in your config: ```ts import { GooglePlacesLookupStrategy } from '@pinelab/vendure-plugin-address-lookup'; plugins: [ AddressLookupPlugin.init({ lookupStrategies: [ new GooglePlacesLookupStrategy({ supportedCountryCodes: ['DE'], apiKey: process.env.GOOGLE_PLACES_APIKEY!, }), ], }), ], ``` The Google places API requires you to input the housenumber and streetname. It will mostly give you a single result, even when multiple results can exists. If that happens, you can pass the postalcode to get a specific result. ```graphql # This example will give you 1 result: the Parkstraße 4 in Osnabrück { lookupAddress( input: { countryCode: "DE", streetName: "Parkstraße", houseNumber: "4" } ) { streetLine1 streetLine2 city province postalCode country countryCode } } ``` ```graphql # This example will give you another single result: the Parkstraße 4 in Löningen { lookupAddress( input: { countryCode: "DE" streetName: "Parkstraße" houseNumber: "4" postalCode: "49624" } ) { streetLine1 streetLine2 city province postalCode country countryCode } } ``` ## Custom lookup strategies If you want to implement your own strategy, for example to support more countries, or use different API's, you can do so by implementing the `LookupStrategy` interface: ```ts import { AddressLookupStrategy } from '@pinelab/vendure-plugin-address-lookup'; export class GermanPostcodeStrategy implements AddressLookupStrategy { readonly supportedCountryCodes = ['DE']; constructor(private readonly input: AddressLookupStrategyInput) {} validateInput?(input: AddressLookupInput): true | string { // Optionally validate the input given by the client } async lookup( ctx: RequestContext, input: AddressLookupInput ): Promise { // Fetch the address from your own API, and map the results to OrderAddress } } ``` 98:Tdec,# Vendure GoedGepickt plugin Plugin for integrating Vendure with GoedGepickt. ## Getting started Vendure's responsibilities vs GoedGepickt's responsibilities: - Vendure is your catalog. If you want a new product, add it in Vendure - GoedGepickt manages all things stock related. StockLevel, size and weight are all managed in GoedGepickt. 1. Add this to your plugin in `vendure-config.ts`: ```ts import { GoedgepicktPlugin } from '@pinelab/vendure-plugin-goedgepickt'; plugins: [ GoedgepicktPlugin.init({ vendureHost: 'https://your-vendure-server.io/', setWebhook: true // Automatically set webhooks in Goedgepickt or not // You can optionally set orders 'on_hold' in Goedgepickt if you'd like determineOrderStatus: (ctx, order) => { if (order.state === 'PaymentAuthorized') { return 'on_hold' as const; } else { return 'open' as const; // This is the default } } }), ... ] ``` 2. Run a [database migration](https://www.vendure.io/docs/developer-guide/migrations/) to add the new fields and entities to your database. 3. Start the server and go to `Settings` > `Channels`, open the channel you want to configure and select the **GoedGepickt** tab. Make sure you have the `SetGoedGepicktConfig` permission. 4. Here you can configure your `apiKey` and `webshopUuid` per channel. When you save the credentials, the plugin will make sure the configured vendureHost is set as webhook for order and stock updates. **The plugin will never delete webhooks**, so if you ever change your url, you should manually delete the old webhook via GoedGepickt. 1. The plugin registers two scheduled tasks. Make sure you have `DefaultSchedulerPlugin` configured in your Vendure config: - **Stock sync** runs every night at 2:00 UTC and pulls stock levels from GoedGepickt into Vendure. - **Product push** runs every Monday at 6:00 UTC and pushes all Vendure products to GoedGepickt. 2. Orders can be manually (re-)pushed to GoedGepickt via the **Push to Goedgepickt** action in the order detail page's action bar dropdown. ### Pickup points / drop off points This plugin uses custom fields on an order as pickup location address. You can set a pickup points on an order with this mutation, the plugin will then send the address to Goedgepickt: ```graphql mutation { setOrderCustomFields( input: { customFields: { pickupLocationNumber: "1234" pickupLocationCarrier: "1" pickupLocationName: "Local shop" pickupLocationStreet: "Shopstreet" pickupLocationHouseNumber: "13" pickupLocationZipcode: "8888HG" pickupLocationCity: "Leeuwarden" pickupLocationCountry: "nl" } } ) { ... on Order { id code } ... on NoActiveOrderError { errorCode message } } } ``` ### Stock locations This plugin **only works with a single stock location** in Vendure. It will not work correctly when you have multiple stock locations configured. GoedGepickt should manage stock for all your locations, and Vendure should only have a single stock location that reflects the total stock managed by GoedGepickt. ## Monitoring and Alerting You should monitor your server logs for the message `Failed to process job sync-order` with severity WARNING. This means an order was not pushed to GoedGepickt. Depending on your job queue implementation this will be retried. In Google Cloud, we create an alert for the following log query: ``` severity>=WARNING "Failed to process job sync-order" ``` 99:T1373,# 3.1.0 (2026-07-29) - Split the single nightly full sync scheduled task into two separate tasks: - `goedgepickt-sync-stock` runs every night at 2:00 AM to pull stock levels from GoedGepickt - `goedgepickt-push-products` runs every Monday at 6:00 AM to push all Vendure products to GoedGepickt - Split `doFullSync()` into `pullAllStocklevels()` and `pushAllProductsToGoedgepickt()` in `GoedgepicktService` # 3.0.1 (2026-07-24) - Include dashboard extensions in dist. # 3.0.0 (2026-07-24) - Replaced manual full sync with an automated nightly scheduled task. The plugin now registers a `ScheduledTask` that runs every night at 2:00 UTC (4:00 CEST) and syncs all enabled channels. - Pull stock levels from GoedGepickt via a button on the product detail page. - **Breaking:** Removed `endpointSecret` from `GoedgepicktPluginConfig`. The `/goedgepickt/fullsync/:secret` endpoint has been removed. - **Breaking:** Removed the `runGoedgepicktFullSync` GraphQL mutation. - **Breaking:** Removed the `GoedGepickt full sync` action bar item from the product list page in the dashboard. Use the scheduled task UI to trigger a full sync. - **Breaking:** The `DefaultSchedulerPlugin` must now be present in your Vendure config for the full sync to run automatically. # 2.4.1 (2026-07-24) - Fix negative freeStock from Goedgepickt by clamping stockOnHand to 0, preventing `error.stockonhand-cannot-be-negative` errors # 2.4.0 (2026-07-21) - Migrated to React Dashboard # 2.3.2 (2026-07-02) - Fix image placeholder detection so Vendure images are sent when Goedgepickt's placeholder is `.jpg` and so new products get the Vendure image # 2.3.1 (2026-06-30) - Send house numbers as strings to Goedgepickt API to prevent "Billing house number moet een tekst zijn" errors - Reduced push order job retries from 10 to 3 # 2.3.0 (2026-08-05) - Upgraded to Vendure 3.6.3 # 2.2.1 (2026-04-23) - Added support for incoming compound product stock update webhook # 2.2.0 (2026-02-05) - Upgraded to Vendure 3.5.3 # 2.1.6 (2025-11-25) - Fix `object null is not iterable at GoedgepicktService.splitHouseNumberAndAddition` for empty house number string # 2.1.4 (2025-11-13) - Documentation update # 2.1.3 (2025-11-06) - Updated official documentation URL # 2.1.2 (2025-10-17) - Allow empty UUID and ApiKey in Goedgepickt config on Channel. # 2.1.1 (2025-06-24) - Improved error logging when incoming webhooks fail - Don't try to transition to Delivered when the order is in PaymentAuthorized state # 2.1.0 (2025-06-04) - Upgrade to Vendure to 3.3.2 # 2.0.8 (2025-05-22) - Try/catch around event handling, to prevent node process crash on error # 2.0.7 (2025-04-24) - Fix for numeric SKU's # 2.0.6 (2025-04-24) - Set correct `main` and `types` paths in package.json, now that we don't export files from outside the root anymore. # 2.0.5 (2025-04-17) - Process incoming stock and order webhooks via the job queue, to prevent webhook disabling in GoedGepickt # 2.0.4 (2025-04-15) - Process stock updates via the job queue, so that it is retried when GoedGepickt returns a `Too Many Attempts` error - Don't use GoedGepickt as fulfilment handler anymore, instead directly move to `Shipped` or `Delivered` on incoming status change. - Update image when the image on GoedGepickt is a placeholder # 2.0.3 (2025-04-03) - Check for undefined or null, to prevent stock updates with 0 being ignored # 2.0.2 (2025-03-20) - Prevent empty update SQL statement - Update stock in batches of 500 # 2.0.1 (2025-03-20) - Setting allocated to 0 on incoming stock updates and full sync # 2.0.0 (2025-03-20) - Removed validating of webhook signature. Fetching stock and order status directly from GoedGepickt on incoming webhook instead. - Moved GG config to Channel Custom Fields, instead of custom UI component. - Breaking: DB migration needed - Breaking: You need to save GoedGepickt credentials on a channel now: Settings > Channel > GoedGepickt custom fields # 1.4.1 (2025-03-18) - Only sync product image on creation, not on update, after complaints from GoedGepickt about too many updates. # 1.4.0 (2024-12-19) - Update Vendure to 3.1.1 # 1.3.2 (2024-11-05) - `orderPlacedAt` field should not be mandatory to push to Picqer # 1.3.0 (2024-10-18) - Allow setting custom order state in GoedGepickt # 1.2.1 (2024-08-04) - Update compatibility range (#480) # 1.2.0 (2024-06-21) - Updated Vendure to 2.2.6 # 1.1.5 (2024-04-30) - Push jobs to queue with promise.all(), so that the fullsync webhook finishes faster, and all jobs are in queue. # 1.1.4 (2024-04-30) - Query by SKU fix for MySQL. `sku = :sku` instead of `productVariant.sku = :sku` # 1.1.3 (2024-04-30) - Log rate limit exceeded as info statements and retry. # 1.1.2 (2024-04-30) - Fix related to stock not updating when a variant with the same SKU has been deleted before. # 1.1.1 (2024-01-16) - Correctly transition to Delivered from Shipped # 1.1.0 (2023-10-24) - Updated vendure to 2.1.1 9a:T6c2,# Vendure E-boekhouden plugin Plugin for syncing orders to the Dutch accounting platform E-boekhouden.nl. ## Getting started Send orders to e-Boekhouden as `GeldOntvangen` mutation and configured `account` and `contraAccount` numbers. Creates a mutation line for each taxrate of the order's tax summary. 1. Add this to your plugin in `vendure-config.ts`: ```ts import { EboekhoudenPlugin } from '@pinelab/vendure-plugin-e-boekhouden' plugins: [ EboekhoudenPlugin.init({ getTaxCode: (ctx, order, taxRate) => { if (order.customFields.VatID && taxRate == 0) { return 'VERL_VERK'; // Reverse charge for EU sales } else if (taxRate == 21) { return 'HOOG_VERK_21'; } else if (taxRate == 9) { return 'LAAG_VERK_9'; } else { Logger.error(`Unknown tax rate ${taxRate} for order ${order.code}`); return 'GEEN'; } }, }), ... ] ``` 2. Start the server and go to `Settings` > `Channels`, open the channel you want to configure and select the **E-boekhouden** tab. Tick `Enabled` and fill in your `Username`, `Security code 1`, `Security code 2`, `Account` and `Contra account`. Configuration is stored per channel as Channel custom fields, so no Admin UI extension needs to be compiled. > The `eBoekhoudenEnabled` toggle controls whether e-Boekhouden is active for a > channel. When it is off (or the config is incomplete), the plugin is disabled > for that channel. ### Development - generate new client 1. Go to https://soap.e-boekhouden.nl/soap.asmx?wsdl and save the wsdl file in `src/client/e-boekhouden-wsdl.xml`. 2. Run `yarn generate-soap-client`. 3. `src/client` will now have an updated and typed soap client for e-Boekhouden. 9b:T21a7,# vendure-plugin-asset-watermark Watermarks image assets in [Vendure](https://vendure.io) by compositing a mark onto the `preview` file the asset server generates. The original `source` file is never modified, so the operation is fully reversible. Compatible with Vendure `^3.0.0`. ## Why the preview Vendure stores every asset twice: the untouched `source`, and a `preview` (max 1600×1600 by default). Every size the storefront ever requests — `thumb`, `small`, `medium`, `large` — is derived by rescaling the **preview**. Watermarking that one file therefore covers every rendition, while leaving a pristine original to fall back to. This is also the only supported extension point: `transformImage()` in the asset server is a module-level function, and `ImageTransformStrategy` can only rewrite transform *parameters*, not inject a compositing step. ## Install ```bash npm i vendure-plugin-asset-watermark ``` `sharp`, `@vendure/core` and `@vendure/asset-server-plugin` are peer dependencies. You already have all three — `sharp` arrives with the asset server plugin — and keeping it a peer is deliberate: a second copy of `sharp` means a second copy of libvips loaded into the same process. `@aws-sdk/client-s3` is optional, and only needed for `S3CachePurgeStrategy`. ## Usage ```ts import { AssetServerPlugin } from '@vendure/asset-server-plugin'; import { AssetWatermarkPlugin, S3CachePurgeStrategy } from 'vendure-plugin-asset-watermark'; export const config: VendureConfig = { plugins: [ AssetWatermarkPlugin.init({ watermarkPath: path.join(__dirname, '../static/watermark.png'), position: 'tile', scale: 0.18, opacity: 0.22, cachePurgeStrategy: new S3CachePurgeStrategy({ bucket: 'my-bucket', nativeS3Configuration: { region: 'us-east-2' }, }), }), AssetServerPlugin.init({ route: 'assets', assetUploadDir: path.join(__dirname, '../static/assets'), previewStrategy: AssetWatermarkPlugin.previewStrategy(), }), ], }; ``` `AssetWatermarkPlugin.init()` must be called before `previewStrategy()`. Then generate the migration for the custom fields the plugin declares: ```bash npx vendure migrate ``` ## Options | Option | Default | Notes | | --- | --- | --- | | `watermarkPath` / `watermarkBuffer` | — | One is required. The image must have an alpha channel. | | `enabled` | `true` | Master switch. | | `scale` | `0.3` | Mark width as a **fraction** of the image width. | | `opacity` | `1` | Applied at runtime, so it can be tuned without re-baking the file. | | `position` | `'southeast'` | Nine anchors plus `'tile'`. | | `margin` | `0.03` | Fraction of the width. Corner positions only. | | `tileAngle` / `tileGap` | `-30` / `0.6` | `position: 'tile'` only. | | `skipMimeTypes` | `['image/svg+xml', 'image/gif']` | SVG rasterises unpredictably; GIF would lose its animation. | | `minWidth` | `200` | Previews narrower than this are left alone. | | `previewMaxWidth` / `previewMaxHeight` | — | Passed through to the underlying `SharpAssetPreviewStrategy`. | | `registerCustomFields` | `true` | Set `false` to skip the two `Asset` custom fields. | | `cachePurgeStrategy` | — | Required for the backfill and the opt-out to work correctly. | ### Sizing is proportional, not absolute `scale` is a fraction because the asset server rescales the preview down to the presets. A mark sized in fixed pixels becomes illegible at `thumb` (150px); a fractional one always covers the same proportion of the image. ### Position and cropping The `tiny` (50px) and `thumb` (150px) presets crop with `sharp.strategy.entropy`, which keeps the highest-detail region and discards the rest. **A corner watermark is frequently cropped away entirely at those sizes.** Use `'center'` or `'tile'` if thumbnail coverage matters. `'tile'` is also the right choice when the subject carries text you must not obscure — engraved part numbers, labels, serial plates. A single large centred mark tends to land right on them. ## Custom fields The plugin adds two fields to the `Asset` entity: - **`skipWatermark`** (boolean) — excludes an asset. Turning it on regenerates a clean preview from the original; turning it off watermarks it again. It renders in the stock Admin UI asset detail view, so no UI recompilation is needed. - **`watermarkedAt`** (datetime, readonly) — the idempotency marker that makes a backfill resumable. > Watermarking cannot be decided per-asset at upload time: `generatePreviewImage()` runs > before the `Asset` row exists and receives no custom fields. Everything supported is > therefore watermarked by default, and `skipWatermark` triggers an after-the-fact > regeneration through the job queue. ## Cache purging The asset server caches each transform at `cache//.`. The md5 covers the transform *parameters*, not the file contents — so when a preview is rewritten at the same path, those keys stay identical and the stale renditions would be served forever. `AssetStorageStrategy` exposes no list operation, so purging is delegated to a `CachePurgeStrategy`: - `S3CachePurgeStrategy` — S3 and S3-compatible backends (MinIO, Cloudflare R2, DigitalOcean Spaces). Needs the optional `@aws-sdk/client-s3` dependency. - `LocalCachePurgeStrategy` — the filesystem-backed `LocalAssetStorageStrategy`. ```ts new LocalCachePurgeStrategy({ assetUploadDir: path.join(__dirname, '../static/assets') }) ``` Implement the interface for any other backend: ```ts export interface CachePurgeStrategy extends InjectableStrategy { purgeForPreview(previewKey: string): Promise; } ``` ## Protecting the original `Asset.source` is exposed on the GraphQL type shared by the Admin and Shop APIs, and the asset server serves `/assets/source/*` without authentication. **The watermark is bypassed by swapping `preview` for `source` in any asset URL.** An optional middleware ships with the plugin: ```ts apiOptions: { middleware: [ { route: '/assets', handler: AssetWatermarkPlugin.sourceGuard(), beforeListen: true }, ], }, ``` The leading slash on `route` matters: `beforeListen` middleware is applied with a raw `app.use(route, handler)`, and express will not match a pathless `'assets'`. > **This is not access control.** Checking that a session cookie is present validates > neither the session nor any permission. It deters casual scraping. For real protection, > block the route at your CDN or load balancer. Check your storefront does not read `asset.source` before enabling it. ## Backfilling an existing catalogue `WatermarkService` exposes the pieces: ```ts const ids = await watermarkService.findCandidates(ctx, { linkedToProductsOnly: true, limit: 25 }); await watermarkService.regeneratePreview(ctx, id, { watermark: true, backup: true }); await watermarkService.restorePreview(ctx, id); // rollback ``` `regeneratePreview` always reads the untouched `source`, so re-running never double-compresses or double-marks. By default it overwrites the preview **at its current path**, which leaves `asset.preview` untouched and spares you a search reindex — at the cost of making the cache purge mandatory. Pass `renamePreview: true` to write a new file name and update the row instead: that busts every cache layer at once, which is what you want for a one-off regeneration that is not followed by a CDN purge. With `backup: true` the previous preview is copied under `preview-backup/` first, which is what makes `restorePreview()` cheap. ### After a bulk backfill Purging your CDN points real traffic at an origin whose derived cache the backfill just emptied, and every miss makes Vendure run a sharp transform on the spot. Request the transforms your storefront actually uses against `127.0.0.1` first, *then* purge — going through the CDN would be answered from its edge cache and never reach the origin. ### A note on browser caches Overwriting a preview in place leaves the URL unchanged, so clients that already cached it keep it until `Cache-Control` expires — the asset server default is `max-age=15552000`, i.e. 180 days. A CDN purge clears the edge but not browsers, and nothing can retroactively shorten an already-issued `max-age`. If you need immediate coverage for returning visitors, have the storefront append a version query param (`?v=2`). Unknown query params are ignored when the asset server computes its cache key, so the same file is served under a URL browsers treat as new. ## Development ```bash npm install npm test npm run build ``` ## License MIT 9c:T58b,# Changelog All notable changes to this project are documented here. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [0.1.1] - 2026-07-31 ### Fixed - Corrected the package author and the LICENSE copyright holder. 0.1.0 was published with the wrong attribution and has been unpublished. ## [0.1.0] - 2026-07-31 Initial release. ### Added - `AssetWatermarkPlugin`, which composites a watermark onto the `preview` file the asset server generates. The original `source` is never modified, so the operation is reversible. - Nine anchor positions plus `tile`, with proportional sizing so the mark stays legible after the asset server rescales a preview down to the smaller presets. - Runtime `opacity`, applied without re-baking the watermark file. - `CachePurgeStrategy` with `S3CachePurgeStrategy` and `LocalCachePurgeStrategy` implementations, for clearing the derived transforms of a regenerated preview. - `skipWatermark` and `watermarkedAt` custom fields on `Asset`, for per-asset opt-out and for tracking a bulk backfill. - `WatermarkService.regeneratePreview()` and `restorePreview()`, for backfilling an existing catalogue and rolling it back. - Optional `createAssetSourceGuard()` middleware, which stops the watermark being bypassed by requesting `/assets/source/*`. 89:{"data":{"items":[{"id":"c30b5b14-dbf9-4966-90f7-1722e2dbffd9","packageName":"@pinelab/vendure-plugin-qls-fulfillment","slug":"qls-fulfillment","name":"QLS Fulfillment","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/b1129afc-f103-4611-8114-5665459acf7d/original.png","downloadCount":301,"latestVersion":"3.2.0","lastPublish":"2026-08-12T12:11:01.168Z","compatibility":">=3.2.0","readme":"$8b","changelog":"$8c","docs":null,"metadataVersion":"3.2.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["shipping-fulfillment"],"createdAt":"2026-05-22T12:37:20.803Z"},{"id":"6733de6a-d7f4-4c46-b782-6aa6b8ebda14","packageName":"@pinelab/vendure-plugin-limited-products","slug":"limited-products","name":"Limited Products","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/7f631d7c-e2be-41e5-9486-fb1d8008b63c/original.png","downloadCount":287,"latestVersion":"3.5.1","lastPublish":"2026-08-04T11:16:33.280Z","compatibility":">=2.2.0","readme":"$8d","changelog":"$8e","docs":null,"metadataVersion":"3.5.1","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["storefront"],"createdAt":"2026-05-22T12:36:55.796Z"},{"id":"56de9f55-0ca2-4d50-8891-f5bef4a621af","packageName":"@pinelab/vendure-plugin-drop-off-points","slug":"drop-off-points","name":"Drop Off Points","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/c07aef71-4661-4037-90c6-e681b294e34e/original.png","downloadCount":285,"latestVersion":"1.3.0","lastPublish":"2026-06-30T09:19:46.004Z","compatibility":">=2.2.0","readme":"$8f","changelog":"# 1.3.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 1.2.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 1.1.2 (2025-11-13)\n\n- Documentation update\n\n# 1.1.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.1.0 (2025-06-04)\n\n- Upgrade to Vendure to 3.3.2\n\n# 1.0.1 (2024-02-04)\n\n- Compatibility version fix\n\n# 1.0.0 (2024-01-30)\n\n- Initial setup\n","docs":null,"metadataVersion":"1.3.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["shipping-fulfillment"],"createdAt":"2026-05-22T12:36:36.537Z"},{"id":"73af5576-e28b-49e6-a11d-c324765cb7f0","packageName":"@pinelab/vendure-plugin-myparcel","slug":"myparcel","name":"MyParcel","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/5bfef668-f762-413b-80e6-5843c39089c9/original.png","downloadCount":285,"latestVersion":"1.8.1","lastPublish":"2026-09-17T11:21:19.315Z","compatibility":">=2.2.0","readme":"$90","changelog":"# 1.8.1 (2026-08-28)\n\n- Updated axios to 1.20.0\n\n# 1.8.0 (2026-07-21)\n\n- Moved configurations from DB into code\n\n# 1.7.1 (2026-06-17)\n\n- Improved error logging when fulfilling to MyParcel fails\n\n# 1.7.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 1.6.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 1.5.2 (2025-11-13)\n\n- Documentation update\n\n# 1.5.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.5.0 (2025-06-04)\n\n- Upgrade to Vendure to 3.3.2\n\n# 1.4.0 (2024-12-19)\n\n- Update Vendure to 3.1.1\n\n# 1.3.1 (2024-08-04)\n\n- Update compatibility range (#480)\n\n# 1.3.0 (2024-06-21)\n\n- Updated Vendure to 2.2.6\n\n# 1.2.0 (2024-01-15)\n\n- Add shipmentStrategy\n- Cleanup of types\n\n# 1.1.0 (2023-10-24)\n\n- Updated vendure to 2.1.1\n","docs":null,"metadataVersion":"1.8.1","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["shipping-fulfillment"],"createdAt":"2026-05-22T12:37:02.673Z"},{"id":"b6ea3792-d70c-4ad2-ba64-6677d11898bc","packageName":"@pinelab/vendure-plugin-validate-cart","slug":"validate-cart","name":"Validate Cart","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":null,"downloadCount":272,"latestVersion":"1.3.1","lastPublish":"2026-07-01T14:50:36.896Z","compatibility":"^3.0.0","readme":"$91","changelog":"$92","docs":null,"metadataVersion":"1.3.1","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["storefront"],"createdAt":"2026-05-22T12:37:37.582Z"},{"id":"56285ee6-14e4-45b4-8a6c-ff60301d86e6","packageName":"@pinelab/vendure-plugin-store-credit","slug":"store-credit","name":"Store Credit","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/b261a03d-b0cc-41da-b7d8-4888853889c1/original.png","downloadCount":270,"latestVersion":"2.1.0","lastPublish":"2026-08-06T12:00:42.453Z","compatibility":null,"readme":"$93","changelog":"$94","docs":null,"metadataVersion":"2.1.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["marketing-seo"],"createdAt":"2026-05-22T12:37:31.297Z"},{"id":"ad55885f-b98f-4469-9398-70d470329176","packageName":"@pinelab/vendure-plugin-google-sheet-loader","slug":"google-sheet-loader","name":"Google Sheet Loader","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/cf1258ed-510e-4b32-8928-ba9ab092bfc6/original.png","downloadCount":264,"latestVersion":"1.3.1","lastPublish":"2026-08-04T11:11:54.087Z","compatibility":"^3.0.0","readme":"$95","changelog":"# 1.3.1 (2026-08-04)\n\n- Include dashboard extensions in dist.\n\n# 1.3.0 (2026-07-21)\n\n- Migrated to React Dashboard\n\n# 1.2.1 (2026-07-10)\n\n- Fixed URL encoding of sheet names in Google Sheets API requests\n\n# 1.2.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 1.1.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 1.0.2 (2025-11-13)\n\n- Documentation update\n\n# 1.0.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.0.0 (2025-10-14)\n\n- Initial release\n","docs":null,"metadataVersion":"1.3.1","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["import-export"],"createdAt":"2026-05-22T12:36:48.641Z"},{"id":"ad3ad51c-26e9-4fd4-a7f5-e8a838533274","packageName":"@pinelab/vendure-plugin-anonymized-order","slug":"anonymized-order","name":"Anonymized Order","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/b2c39eea-914d-42e5-820e-8917fce5980e/original.png","downloadCount":263,"latestVersion":"1.6.0","lastPublish":"2026-07-21T17:32:06.695Z","compatibility":">=2.2.0","readme":"$96","changelog":"# 1.6.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 1.5.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 1.4.2 (2025-11-13)\n\n- Documentation update\n\n# 1.4.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.4.0 (2025-06-04)\n\n- Upgraded to Vendure 3.3.2\n\n# 1.3.0 (2024-12-19)\n\n- Update Vendure to 3.1.1\n\n# 1.2.1 (2024-08-04)\n\n- Update compatibility range (#480)\n\n# 1.2.0 (2024-06-21)\n\n- Updated Vendure to 2.2.6\n\n# 1.1.0 (2024-06-14)\n\n- Allow overriding the default removal of fields with the custom strategy\n\n# 1.0.1 (2023-12-29)\n\n- Fixed exposed fields bug reported in [here](https://github.com/Pinelab-studio/pinelab-vendure-plugins/issues/316)\n\n# 1.0.0 (2023-12-28)\n\n- Created the plugin\n","docs":null,"metadataVersion":"1.6.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["other"],"createdAt":"2026-05-22T12:36:29.396Z"},{"id":"82c88875-8624-42e1-afd8-5a6924914398","packageName":"@pinelab/vendure-plugin-address-lookup","slug":"address-lookup","name":"Address Lookup","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/e89df479-86a9-441a-af75-05fbd75a7a23/original.png","downloadCount":252,"latestVersion":"2.2.0","lastPublish":"2026-07-10T12:23:18.459Z","compatibility":">=2.2.0","readme":"$97","changelog":"# 2.2.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 2.1.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 2.0.1 (2026-02-04)\n\n- Log addditional error details for BAG API\n\n# 2.0.0 (2025-12-24)\n\n- Replaced Postcode.tech API with BAG api, because Postcode.tech is no longer available\n\n# 1.2.2 (2025-11-13)\n\n- Documentation update\n\n# 1.2.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.2.0 (2025-06-11)\n\n- Added Google Places API strategy for global address lookup\n- BREAKING: Input `postalCode` is now optional\n\n# 1.1.1 (2025-06-04)\n\n- Fixed bug where PostNL house number addition was not being returned on streetline 2\n\n# 1.1.0 (2025-06-04)\n\n- Upgraded to Vendure 3.3.2\n\n# 1.0.0 (2025-06-04)\n\n- Fixed bug where house number addition was not being sent to PostNL API\n- Made this the official 1.0 release\n\n# 0.0.1 (2025-05-07)\n\n- Initial release\n","docs":null,"metadataVersion":"2.2.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["shipping-fulfillment"],"createdAt":"2026-05-22T12:36:24.357Z"},{"id":"501fd348-522f-42c4-a3b1-a83aca5b144d","packageName":"@pinelab/vendure-plugin-goedgepickt","slug":"goedgepickt","name":"GoedGepickt","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/0368aa99-e9cb-43dd-b861-9b52649bfcce/original.png","downloadCount":251,"latestVersion":"3.1.0","lastPublish":"2026-07-29T13:37:22.763Z","compatibility":">=2.2.0","readme":"$98","changelog":"$99","docs":null,"metadataVersion":"3.1.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["shipping-fulfillment"],"createdAt":"2026-05-22T12:36:44.433Z"},{"id":"436cc38e-fe37-49b4-aba1-3a3a3fc3aee6","packageName":"@pinelab/vendure-plugin-e-boekhouden","slug":"e-boekhouden","name":"E-boekhouden","description":null,"registry":"npm","repositoryUrl":"https://github.com/Pinelab-studio/pinelab-vendure-plugins","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/44031381-4f5c-4a96-a523-750ea66aaab3/original.png","downloadCount":225,"latestVersion":"2.3.0","lastPublish":"2026-07-21T17:32:09.926Z","compatibility":">=2.2.0","readme":"$9a","changelog":"# 2.3.0 (2026-07-21)\n\n- Moved configurations from DB into code\n\n# 2.2.0 (2026-08-05)\n\n- Upgraded to Vendure 3.6.3\n\n# 2.1.0 (2026-02-05)\n\n- Upgraded to Vendure 3.5.3\n\n# 2.0.0 (2025-11-25)\n\n- Add support for custom VAT code strategy to define the VAT code to send to e-boekhouden\n\n# 1.4.2 (2025-11-13)\n\n- Documentation update\n\n# 1.4.1 (2025-11-06)\n\n- Updated official documentation URL\n\n# 1.4.0 (2025-06-04)\n\n- Upgrade to Vendure to 3.3.2\n\n# 1.3.0 (2024-12-19)\n\n- Update Vendure to 3.1.1\n\n# 1.2.1 (2024-08-04)\n\n- Update compatibility range (#480)\n\n# 1.2.0 (2024-06-21)\n\n- Updated Vendure to 2.2.6\n\n# 1.1.0 (2023-10-24)\n\n- Updated vendure to 2.1.1\n","docs":null,"metadataVersion":"2.3.0","partnerId":"a87615d5-735c-494b-b572-84feaab866d8","categories":["tax-compliance"],"createdAt":"2026-05-22T12:36:38.530Z"},{"id":"8f252c4d-6b6e-4bf1-940d-c6d682f166da","packageName":"vendure-plugin-asset-watermark","slug":"vendure-plugin-asset-watermark","name":"Vendure Plugin Asset Watermark","description":null,"registry":"npm","repositoryUrl":"https://github.com/dtrejogo/vendure-plugin-asset-watermark","iconUrl":"https://minio.minio--wq6vpbzhh2fw.addon.code.run/api-public/plugin-icon/f704c93c-6034-4395-9dcb-57a19d28dc43/original.png","downloadCount":193,"latestVersion":"0.1.1","lastPublish":"2026-07-31T11:53:34.139Z","compatibility":"^3.0.0","readme":"$9b","changelog":"$9c","docs":null,"metadataVersion":"0.1.1","partnerId":"48a5b700-2606-4276-8765-2e19789e884b","categories":["admin-extensions"],"createdAt":"2026-08-19T14:58:33.380Z"}],"total":44,"page":3,"pageSize":12},"error":"$undefined"}

Plugin Directory

Plugin Directory