A build-to-order Magento 2 / Adobe Commerce extension that surfaces unified customer history, loyalty balance and clienteling notes at the point of sale so staff personalize in-store service from the same data as the web store. One-time license from $299.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.

A build-to-order Magento 2 / Adobe Commerce extension that surfaces unified customer history, loyalty balance and clienteling notes at the point of sale so staff personalize in-store service from the same data as the web store.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Magento 2 Customer Profiles & CRM at POS is a custom-built extension that turns your point of sale into a clienteling station. When a cashier or sales associate looks up a customer at the till, they see the same unified profile your web store already holds: lifetime web and in-store purchase history, loyalty balance and tier, saved addresses, and free-form notes and tags your team adds over time.
Unified online + in-store customer profile sourced from Magento's native CustomerRepositoryInterface service contract, so the till and web store read one record
Full purchase history at the point of sale — web orders plus in-store orders folded together via an observer on sales_order_place_after
Loyalty balance and tier display through a pluggable adapter (Adobe Commerce Reward Points or your existing rewards extension)
Clienteling notes and tags stored in a dedicated db_schema.xml table, attached to the customer and visible to every authorized associate
Quick customer creation at the till with minimal required fields, writing through the standard customer service contract (no orphaned records)
Barcode / loyalty-card and phone/email lookup endpoints exposed over REST and GraphQL with rate-limited, token-authenticated access
Technically, this is a real Magento 2 module delivered under app/code/Ecosire/PosCustomerCrm (PSR-4, composer.json + module.xml). It extends the native Magento\Customer data via service contracts (CustomerRepositoryInterface), stores clienteling notes/tags in a dedicated table provisioned by a declarative schema db_schema.xml, and exposes everything to your POS through a versioned REST and GraphQL layer guarded by admin ACL (acl.xml) and OAuth/integration tokens. We wire behavior through dependency injection (di.xml), plugins/interceptors to enrich order data, and observers on sales_order_place_after so in-store orders fold back into the same purchase history. Loyalty balance is read through an adapter that targets either Adobe Commerce native Reward Points or your existing rewards extension.
This is not an instant Adobe Commerce Marketplace download. ECOSIRE builds it to your POS stack and Magento version, installs it on your environment (setup:upgrade, setup:di:compile), and supports it afterward. Works on Magento Open Source and Adobe Commerce 2.4.x, and is shaped around your actual till workflow — barcode/loyalty-card lookup, multi-store views, and the customer attributes your associates rely on.
Runs one or more physical stores and wants associates to greet customers with their web purchase history, loyalty tier and past preferences already on screen — turning the till into a relationship tool, not just a checkout.
Owns the Magento store and is tired of web and in-store being two disconnected worlds. Needs a single customer record across channels so marketing, loyalty and service all reference the same lifetime value.
Maintains the point-of-sale stack and needs a clean, ACL-guarded REST/GraphQL contract to pull customer profiles and push in-store orders, built to Magento standards so it survives 2.4.x upgrades.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Magento 2 Customer Profiles & CRM at POS-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Magento 2 Customer Profiles & CRM at POS“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Unified web + in-store profile from one Magento customer record | ||||
| Purchase history (web + in-store) surfaced at the till | ||||
| Loyalty balance & tier shown to associates at POS | ||||
| Clienteling notes & tags on the customer record | ||||
| Built to your specific POS system & Magento edition/version | ||||
| Installed & supported by the engineers who built it | ||||
| Upgrade-safe (service contracts, db_schema.xml, no core edits) | ||||
| Instant self-service download from a marketplace |
No. This is a build-to-order extension. ECOSIRE writes the module to fit your POS system, Magento edition and 2.4.x version, then installs it on your environment. There is no Adobe Commerce Marketplace listing or instant-download link — the value is that it matches your actual till workflow and data.
Typical delivery is about 2 to 4 weeks from kickoff, depending on your POS system, loyalty source and how much in-store-order history needs to be reconciled. After a short scoping call we confirm a firm timeline, build on a branch, demo on your staging environment, then install to production during a low-traffic window.
Every build includes a post-launch warranty period covering defects. After that, an optional support plan keeps the module compatible across Magento / Adobe Commerce 2.4.x security and minor releases, handles small enhancements, and gives you a direct line to the engineers who built it. We don't push silent auto-updates to your production store.
Yes. The module is built against Magento 2 service contracts and the framework, so it runs on both Magento Open Source and Adobe Commerce 2.4.x. The loyalty display adapts to your rewards source: Adobe Commerce native Reward Points, or a third-party loyalty extension on Open Source.
It's built the standard way — declarative db_schema.xml, service contracts returning DTOs, di.xml-based wiring and proper plugins rather than core hacks — so it survives setup:di:compile and 2.4.x upgrades. We never edit core files. If a major version (e.g. a future 2.5) requires changes, that's covered under a support plan.
All POS-facing endpoints are exposed over REST/GraphQL behind OAuth/integration-token authentication, rate-limited, and gated by Magento admin ACL resources so only authorized roles can view history, edit notes or create customers. Notes and tags also participate in Magento's customer privacy (anonymize/erase) flows for GDPR compliance.
A build-to-order Magento 2 / Adobe Commerce extension that surfaces unified customer history, loyalty balance and clienteling notes at the point of sale so staff personalize in-store service from the same data as the web store.