PHPackages attlaz/magento2-module-attlaz-order - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. attlaz/magento2-module-attlaz-order ActiveMagento2-module attlaz/magento2-module-attlaz-order =================================== Attlaz Magento2 Order Module 3.2.0(1w ago)012↓66.7%1OSL-3.0PHPPHP >=8.2CI failing Since Apr 4Pushed 1w agoCompare [ Source](https://github.com/Attlaz-Platform/magento2-module-attlaz-order)[ Packagist](https://packagist.org/packages/attlaz/magento2-module-attlaz-order)[ Docs](https://attlaz.com)[ RSS](/packages/attlaz-magento2-module-attlaz-order/feed)WikiDiscussions master Synced 1w ago READMEChangelogDependencies (27)Versions (26)Used By (0) Magento2 Module Attlaz Order ============================ [](#magento2-module-attlaz-order) [![Latest Stable Version](https://camo.githubusercontent.com/00036021407c40c59ebaf0803d8d9f62af2e3c5f78e8db4dfd8273346a564a03/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f6174746c617a2f6d6167656e746f322d6d6f64756c652d6174746c617a2d6f726465722e737667)](https://packagist.org/packages/attlaz/magento2-module-attlaz-order) [Attlaz](https://attlaz.com) is a cloud-based integration, automation and data management platform. Getting started --------------- [](#getting-started) ``` composer require attlaz/magento2-module-attlaz-order ``` Requirements ------------ [](#requirements) - PHP >= 8.2 - Magento Open Source / Adobe Commerce 2.4.6+ - [`attlaz/magento2-module-attlaz-base`](https://packagist.org/packages/attlaz/magento2-module-attlaz-base) 3.2+ How order synchronization works ------------------------------- [](#how-order-synchronization-works) The module hands Magento orders to an Attlaz flow. Four fields are stored on each order and mirrored to the sales order grid: - `attlaz_external_id` — set once the order has been handed to Attlaz; its presence marks the order as synced - `attlaz_sync_id` — the Attlaz flow-run id used to poll status - `attlaz_sync_status` — one of `requested`, `running`, `complete`, `failed`, `invalid`, `unknown` - `attlaz_sync_time` — timestamp of the last sync attempt Two cron jobs run every 5 minutes (default group), up to 20 orders per run: - `attlaz_order_sync_unsynced` — requests a flow run for every order without an `attlaz_external_id` - `attlaz_order_sync_status` — polls in-progress flow runs and updates `attlaz_sync_status` The cron only runs when **Enable order sync** is on and, for flow-based sync, a flow is configured. Manual sync works regardless — the **Sync** button on the admin order view, or: ``` bin/magento attlaz:sync:orders bin/magento attlaz:sync:order-statuses ``` A failed request marks the order `failed` and leaves `attlaz_external_id` empty, so the next cron run retries it. There is **no retry limit or backoff**: a permanently failing order is retried indefinitely, one request and one log line per run. Transient failures self-heal; permanent ones need looking at (a capped retry may come later). Configuration ------------- [](#configuration) Stores → Configuration → Attlaz → **Order sync**: FieldEffect**Enable order sync**Master switch for the cron sync. **Off by default** (since 3.1.0), so an upgrade never starts syncing on its own.**Synchronize order key**The Attlaz flow that receives the orders. Not needed when a custom plugin on `SyncOrderCommand::sync()` drives the sync instead.**Sync orders from date**Only orders created on or after this date are synced. Empty = no cutoff; set it on first rollout to avoid re-sending your order history.**Order statuses to sync**Only orders with these statuses are synced. **Empty syncs nothing** — an empty filter means "not configured yet", not "send everything".### Filtering on status [](#filtering-on-status) Orders sharing a state don't all mean the same thing: state `new` holds both an unpaid order waiting for its payment provider and a pay-on-delivery order that is ready for the ERP the moment it is placed. Status is the axis that tells them apart — create your own (Stores → Order Status → Create New Status), assign it to the state, and point the payment method's **New Order Status** at it (Stores → Configuration → Sales → Payment Methods). Only orders placed with that method carry it. > **Check the code, not the label.** "Pending" is state `new`'s default status; "Pending Payment" is `pending_payment`, an order whose payment has *not* arrived. The list prints the raw code for that reason. Two more things worth knowing: a status created later is not synced until you select it here (deliberate — a new status entering the sync unnoticed is how unpaid orders reach an ERP), and other extensions (analytics, marketing, feeds) keep their own status filters, so repointing a payment method at a new status can quietly drop its orders out of those. *Order states to sync* existed in 3.1.0–3.2.x and was removed in 3.3.0 — select the statuses belonging to those states instead. Getting Help ------------ [](#getting-help) - [Attlaz Documentation](https://docs.attlaz.com) - [Issue Tracker](https://github.com/Attlaz-Platform/magento2-module-attlaz-order/issues) — questions, bug reports and feature requests - Developer support: ### Health Score 53 — FairBetter than 96% of packages Maintenance98 Actively maintained with recent releases Popularity8 Limited adoption so far Community7 Small or concentrated contributor base Maturity83 Battle-tested with a long release history Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~112 days Recently: every ~9 days Total 25 Last Release 11d ago Major Versions 2.4.2 → 3.0.02026-07-11 PHP version history (4 changes)2.0.0PHP ~7.0.6|~7.1.0|~7.2.0 2.3.0PHP ^7.4 | ^8.1 2.4.0PHP ^8.1 3.0.0PHP >=8.2 ### Community Maintainers ![](https://www.gravatar.com/avatar/9477f1195b4f7dcf4eaedfcbc4f3721a2b9e96a50400b6b168307587769381c2?d=identicon)[Echron](/maintainers/Echron) --- Top Contributors [![Echron](https://avatars.githubusercontent.com/u/2070180?v=4)](https://github.com/Echron "Echron (84 commits)") --- Tags Connectionsynchronizeorderattlazipaas ### Code Quality TestsPHPUnit Static AnalysisPHPStan Code StylePHP CS Fixer Type Coverage Yes ### Embed Badge ![Health badge](/badges/attlaz-magento2-module-attlaz-order/health.svg) ``` [![Health](https://phpackages.com/badges/attlaz-magento2-module-attlaz-order/health.svg)](https://phpackages.com/packages/attlaz-magento2-module-attlaz-order) ``` ### Alternatives [mollie/magento2 Mollie Payment Module for Magento 2 1142.0M17](/packages/mollie-magento2)[buckaroo/magento2 Buckaroo Magento 2 extension 32426.0k8](/packages/buckaroo-magento2)[zwernemann/module-withdrawal Magento 2 EU Withdrawal Button Module - Adds a withdrawal/revocation button for orders in compliance with EU Directive (EU) 2023/2673 2610.9k2](/packages/zwernemann-module-withdrawal)[dotdigital/dotdigital-magento2-extension Dotdigital for Magento 2 50406.2k23](/packages/dotdigital-dotdigital-magento2-extension)[yireo/magento2-emailtester2 Preview transactional emails and test send them in your backend 34441.8k](/packages/yireo-magento2-emailtester2)[loki/magento2-admin-components Admin Panel grids and forms created via Loki Components 178.3k9](/packages/loki-magento2-admin-components) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)