No. This is a build-to-order extension. ECOSIRE engineers the `Ecosire_GiftCard` module against your specific Magento version and business rules, installs it on your staging instance, and hands it over. There is no instant Marketplace cart-and-download — you get a module built and tested for your actual store.

Typical delivery is 10–15 business days from the kickoff call, depending on scope — POS integration, custom print templates, and bespoke accounting hooks add time. We confirm a firm timeline in writing once we review your Magento version, edition (Open Source vs Adobe Commerce), and POS setup. Rush options are available on request.

Every build includes a post-delivery support window for bug fixes and configuration help. Because the code lives in your repository under `app/code/Ecosire/GiftCard`, you own it outright. We offer optional retainer plans for compatibility updates against new Magento/Adobe Commerce releases, security patches, and feature additions.

Yes — that's a core design goal. Store credit and gift card balance are exposed through Magento service contracts over REST and GraphQL, so the same balance is applied whether the customer checks out on the website or at an in-store POS terminal. We wire the integration to your specific POS during the build.

Both. The module is written against standard Magento 2 framework APIs (service contracts, plugins, observers) so it runs on Magento Open Source and Adobe Commerce. Note that Adobe Commerce already ships native gift card and store credit features; we'll tell you honestly during scoping whether a custom build or extending the native modules is the better fit for you.

Yes. Codes are generated with cryptographically strong randomness, stored hashed, and minted only on the `order_invoice_pay` event after payment capture — never at order placement. Redemption is single-use and transactional, every balance change is written to an append-only ledger, and all admin balance adjustments are ACL-gated and audited.