Abeta for Magento 2





Powerful Magento 2 Extension for Abeta OCI and cXML PunchOut
Connect your Magento 2 store to enterprise procurement systems
B2B customers increasingly buy through procurement platforms such as SAP, Coupa, Oracle, and similar systems. Without a proper OCI or cXML PunchOut integration, Magento 2 merchants often depend on manual order transfers, spreadsheets, or custom workarounds. This creates delays, incorrect order data, and extra administration for both the seller and the buyer. The Abeta PunchOut integration for Magento 2 connects your webshop to enterprise procurement workflows, allowing buyers to start in their procurement system, shop in Magento 2, and return the cart with the correct product data. Built for B2B stores, agencies, and developers, this module supports reliable PunchOut sessions, user rotation, and complex product structures.

Enables OCI and cXML PunchOut flows for Magento 2 through Abeta.
Prevents shared-cart issues by isolating PunchOut sessions per buyer.
Why This Magento 2 PunchOut Module Matters
In many B2B organisations, purchasing must happen inside an ERP or procurement platform. PunchOut makes that process easier by allowing buyers to select products in your Magento 2 store while keeping the purchase request inside their own procurement workflow.
Instead of manually retyping SKUs, product names, quantities, prices, or configuration details, the buyer fills the cart in Magento 2 and sends it back to the procurement system in a structured format. This reduces manual work, lowers the risk of order mistakes, and gives enterprise customers a buying experience that matches their internal approval process.
For Magento 2 merchants, this creates a more professional B2B sales channel. It helps serve larger customers that require OCI or cXML PunchOut support and reduces the operational overhead normally involved in procurement-based ordering.
Isolated carts for parallel PunchOut users
Magento 2 does not support multiple active sessions on the same customer account. In a typical PunchOut setup, several employees may enter the webshop through one corporate procurement account. Without additional handling, those buyers can end up sharing the same Magento cart, causing overwritten quotes, mixed items, and incorrect purchase requests.
The Abeta PunchOut module solves this with a user rotation approach. When a PunchOut login is detected, Magento automatically assigns an available rotation user in the background. Each buyer receives an isolated Magento session and quote, while the technical rotation users remain invisible to the customer.
This keeps every PunchOut cart separate, even when multiple buyers from the same organisation are shopping at the same time. :::
Isolates carts for concurrent PunchOut buyers.
Prevents cart overwrites and mixed purchase requests.
Supports stable B2B procurement workflows for shared accounts.
Support for Unique and Configurable Products
Many B2B Magento 2 catalogues include products that are configured per order. Examples include configurable products, custom compositions, products with attachments, or items with project-specific text and specifications. In these cases, the final ordered item is not always represented by one simple static SKU.
The Abeta OCI and cXML PunchOut integration supports these scenarios by returning the relevant configuration data in the PunchOut payload. This gives the procurement system the information needed to create a complete purchase request.
For merchants, this reduces back and forth communication after order approval. For buyers, it creates a clearer procurement flow where the selected Magento product configuration is carried back into their internal system.
Key Features of the Magento 2 Abeta PunchOut Integration
- Connects Magento 2 to OCI and cXML PunchOut through Abeta endpoints.
- Assigns rotation users automatically to support parallel buyers.
- Returns complete cart data to procurement systems after shopping.
- Supports configurable products and unique order compositions.
- Integrates with Magento 2 customer, session, and cart logic.
- Keeps standard Magento checkout behaviour available when needed.
Technical Details and Who It’s For
The Abeta PunchOut integration is configured directly in the Magento admin under Stores > Configuration > Magmodules > Abeta PunchOut Integration. From this section, merchants or developers can configure the OCI and cXML endpoints, authentication details, and rotation user mapping required for stable PunchOut sessions.
When a PunchOut request is received, Magento 2 starts a dedicated customer session using an available rotation account. The buyer can then browse the Magento 2 store, add products to the cart, and configure products where needed. Once the buyer finishes the shopping flow, the module returns the quote contents to the procurement environment in the expected OCI or cXML structure.
The extension integrates with Magento customer, quote, session, and cart workflows. Depending on the project setup, cron can be used for logging, monitoring, or synchronisation processes. Abeta account access and API credentials are required to complete the connection.
This module is built for Magento 2 store owners selling to enterprise customers, e-commerce managers implementing procurement buying flows, Magento agencies delivering PunchOut projects, and developers who need a reliable foundation for Abeta-based OCI or cXML integrations. :::
Business Impact for B2B Magento Stores
A reliable PunchOut integration helps Magento 2 merchants serve enterprise customers more efficiently. Buyers can continue using their own procurement platform, while still shopping in the Magento 2 storefront with accurate product information, pricing, and configuration options.
By returning structured cart data directly to the procurement system, the module reduces manual entry, prevents copied SKU mistakes, and limits pricing or quantity mismatches. This improves the purchasing experience for buyers and lowers the number of order corrections handled by your team.
For many B2B stores, OCI and cXML PunchOut support can also improve conversion from larger customers who require procurement compliance before placing orders.
Knowledgebase
All familiar Help articles
A list of the most frequently asked questions from the Abeta extension for Magento 2. We've tried our best to help you with the installation, configuration and troubleshooting. If you do not find the answer you were looking for, you can always send us a message through this form.
Installation articles
Installation using Composer (recommended)Configuration
Changelog 1.9.0 is released on 3 December 2025
Our plugins are regularly updated to ensure compatibility with the latest Magento release.
-
Features:
- Added enhanced quote item options with decoded JSON values and labels. Improvements:
- Collect totals before calculating shipping rates to ensure accurate calculations. Minimum requirements:
- Magento 2.3.x & PHP 7.4
-
Features:
- Added email fallback for customer lookup.
- Added support for multiple products and return quote data.
- Appended shipping data to return data. Compatibility:
- Magento 2.3.x and up
- PHP 7.4 and up
-
Features:
- Implemented new 'logging_only' flow Improvements:
- Corrected a typo Compatibility:
- Magento 2.3.x and up
- PHP 7.4 and up
-
Features:
- Added support for getting product by SKU and fixed casting
- Added support for PHP 8.4 and Magento 2.4.8
-
Changes:
- Add ItemData WebAPI to fetch product pricing
- Added regenerate session ID after login
- Upgrade PHP & Magento Versions in CI Workflow
-
Changes:
- Added option to pass on a redirect url in login action
- Added option to add custom css to button
-
Changes:
- Added two new options to API
-
Changes:
- Unset session data after redirect
- Create db_schema_whitelist.json
-
Changes:
- Use fallback to store address for calculating shipping price
-
Changes:
- Add child data of parents to export
-
Changes:
- Fix issue with products without category
-
Changes:
- Added option to toggle usage of modal in cart
-
Changes:
- Added check on default addresses
- Fixed the z-index for checkout modal
- Remove 'mixed' type declaration (PHP 74)
100% Unencrypted Code quality guaranteed.

Adobe Commerce Marketplace Approved
This extension is listed on the official Adobe Commerce Marketplace and has passed their review process for code quality, performance and security.
Adobe Marketplace approval means the extension follows Magento coding standards and integrates properly with the platform. Updates go through the same review process.

Hyvä Compatible Plugin
This extension includes full support for Hyva Themes. All frontend components, widgets and templates work natively with Hyva's Alpine.js and Tailwind CSS stack.
The extension works out of the box on Hyva and is tested with every new Hyva release to ensure continued compatibility.

GraphQL Made Ready
This extension exposes its data and configuration through Magento's GraphQL API. You can query and mutate data directly from headless frontends or custom applications.
The GraphQL schema follows Magento's conventions and covers all key functionality of the extension. This makes it ready for PWA Studio, Vue Storefront or any other headless setup.

Magento Cloud Support
This extension is fully compatible with Adobe Commerce Cloud (Magento Cloud). It works with the read-only filesystem, the build and deploy pipeline and cloud-specific caching layers.
No additional configuration or workarounds are needed for cloud environments. The extension handles static content deployment and config management the same way as on-premise installations.

Private Composer Repo
After purchase you get access to a private Composer repository with personal credentials. Install and update the extension with a single composer command, just like any other dependency.
Your Composer credentials are available in your account dashboard. Updates are published to the repository as soon as a new version is released, so you always have access to the latest version.