Abeta for Magento 2
Test out this module for Free
Abeta
Check your email
We've sent a confirmation link. Click it to spin up your demo.
Setting up your demo...
This usually takes a few minutes. You can close this modal or wait for the result — we'll also send you an email when it's ready.
You're in the queue
Position: #
All demo slots are currently in use. You'll receive an email as soon as your demo is ready.
Your demo is ready!
Expires:
Credentials have also been sent to your email.
Something went wrong
We couldn't set up your demo. Please try again or contact support.





Abeta PunchOut for Magento 2
Let B2B Buyers Order from Their Procurement System
Abeta PunchOut connects your Magento 2 store to Abeta, the service that links webshops to procurement systems over OCI and cXML. A buyer starts in the procurement system, is logged in to your store with a one-time link and fills the cart with the prices of their own customer account. It is the official Abeta plugin for Magento 2, developed by Magmodules.
In the cart the buyer clicks "PunchOut" instead of "Proceed to Checkout". The module sends the cart to Abeta as JSON, with prices, VAT, options and shipping costs, and returns the buyer to the procurement system, where the purchase request follows the customer's own approval process.
Setup takes two fields in the Magento admin: "Enabled" and "Abeta API key".

One API Key
Turn on "Enabled" and enter the "Abeta API key". There are no endpoints or user mappings to set up in Magento.
One-Time Login Link
Abeta requests a login URL for every session. The token behind it is deleted the moment it is used.
An Account per Buyer
With a buyer_email in the request every buyer gets an own customer account, with the customer group and VAT number of the main account.
PunchOut Button in the Cart
During a session the cart shows the "PunchOut" button and hides "Proceed to Checkout", so orders go through the procurement system.
Complete Cart Data
Prices with and without VAT, child products, custom options, attribute labels, categories and a shipping line go back to Abeta as JSON.
Logging in the Admin
Two log files of its own and buttons that show the last 100 debug and error records without server access.

Connect with One API Key and a One-Time Login
The settings are under Stores > Configuration > Services > PunchOut. Set "Enabled" to "Yes" and enter the "Abeta API key". There are no endpoints or user mappings to configure in Magento: Abeta sends the session ID and the return URL with every login request.
For each session Abeta calls POST /V1/abeta/login with the e-mail address and password of the customer account, a session ID and the API key. The module compares the key with the setting, authenticates the customer and returns a login URL that works once. The token is deleted as soon as it is used, so a link from a browser history cannot be opened a second time.
Options per Session
Abeta can send extra parameters with the login:
empty_cart_on_login: on by default. A cart with items from an earlier visit is set to inactive, so the buyer starts empty.logout_on_punchout: on by default. The customer session ends after the cart has been sent.login_only: logs the buyer in without a PunchOut session, so the regular checkout stays available.redirect_url: the page the buyer lands on after the login, for example a category or a product.
A Customer Account for Each Buyer
Several employees of one organisation often enter the store through the same procurement account. When Abeta sends a buyer_email with the login, the module looks up the customer account with that address or creates it. Each buyer then has an own account and an own cart, so two colleagues who shop at the same time do not end up in each other's items.
A new buyer account gets the first and last name from the request (buyer_first_name and buyer_last_name) or, when those are missing, from the main account. The customer group and VAT number are copied from the main account and compared again at every login. Change the customer group of the main account and the buyers follow at their next session, so prices that depend on the customer group stay the same for the whole organisation.
Buyer accounts are regular Magento customers, visible under Customers > All Customers. Without a buyer_email all buyers log in to the main account and share its cart. Stores that share customer accounts per website are supported: the customer is looked up on the website of the account.


PunchOut Button and Order Overview in the Cart
During a PunchOut session the cart shows a button with the text from "Return Button Label", which is "PunchOut" by default. "Proceed to Checkout" is hidden and a buyer who opens the checkout URL is sent back to the cart. An order can therefore not be placed in the store by accident, outside the procurement system. Outside a session nothing changes: the button only appears when the module is enabled and an Abeta session is active.
With "Use Modal" set to "Yes", the default, the button opens a window titled "Order data for PunchOut session" with the product names and quantities, including the shipping line. The buyer confirms with the button or clicks "Close" to continue shopping. Set it to "No" and the button sends the cart straight away.
"Custom Css" takes CSS that is added to the cart page during a session, for example to match the button to your theme without a template override.
Complete Cart Data Back to the Procurement System
When the buyer confirms, the module posts the cart as JSON to the return URL that Abeta supplied at login. Abeta turns it into the OCI or cXML message the procurement system expects. Magento itself does not generate OCI or cXML. After the transfer the cart is set to inactive and the buyer is redirected to the return URL.
Each line contains:
- SKU, title, quantity and product type
- Price including and excluding VAT, VAT percentage and line total
- The image URL of the product
- The child products of configurable and bundle products
- Custom options with their label and the chosen value
- Product attributes, with dropdown values as readable labels instead of option IDs
- Category names
Shipping Costs as a Separate Line
Shipping goes along as a separate line with the SKU shipping, so the purchase request can include the delivery costs. When a "Default Shipping Method" is set, the module applies it to the cart before the export. The list shows all shipping methods in the store, including those of carriers that are not active. If the cart has no shipping address yet, the module uses the default shipping address of the customer or, when there is none, the country and postcode of the store.


Debug Mode and a Log Viewer in the Admin
A PunchOut connection has three parties: the procurement system, Abeta and your store. When a session fails, you want to see what arrived in Magento. The module has two log files of its own, var/log/abeta-debug.log and var/log/abeta-error.log, separate from the Magento system log.
The debug log receives the login request, the cart export and the call to the return URL of Abeta with the HTTP status of the response. Failures, such as missing session data or a shipping method that could not be applied, go to the error log.
Under "Debug & Logging" you find "Debug Mode", which is off by default, and two buttons that show the last 100 debug and error records in the admin. Support staff can check a session there without SSH access to the server.
Abeta PunchOut for Magento 2: Technical Details for Developers and Store Owners
The Advantages for Developers
- Installation:
composer require abeta-io/magento2, then enable the moduleAbeta_PunchOut. Version 1.10.1 requires PHP 7.4 or higher. - Four REST endpoints:
POST /V1/abeta/login,GET /V1/abeta/cart,GET /V1/abeta/checkoutandPOST /V1/abeta/itemData. The first and the last check the API key, the other two work on the storefront session of the buyer. itemDatabuilds a quote for a customer and one or more products, by SKU or product ID, and returns prices, product attributes and the available shipping rates. Abeta can request prices this way without a storefront session.- After the token login the module refreshes the private content of Magento, so the minicart and the customer data are correct on the first page.
- The cart button is a block in the
cart.summarycontainer with the templateAbeta_PunchOut::cart/button.phtml. The order window uses the standard Magento UI modal. - The module does not add cron jobs.
Good to Know for Store Owners
- You need an API key from Abeta. Abeta handles the connection to the procurement system of your customer, for example Coupa, Oracle or SAP Ariba.
- "Enabled", "Abeta API key" and the four fields under "Settings" can be set per website and per store view.
- Regular customers notice nothing: outside a PunchOut session the cart and the checkout work as before.
- Every buyer account is a normal customer in Magento, in the customer group of the main account, so existing group prices and catalog rules keep applying.
Ready to Connect Magento 2 to Abeta PunchOut?
Install the module, enter your API key and let buyers order from their own procurement system, with a separate account per buyer and complete cart data on every purchase request.
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.10.3 is released on 18 November 2026
Our plugins are regularly updated to ensure compatibility with the latest Magento release.
100% Unencrypted Code quality guaranteed.
Quality
Approved, Compatible and Tested

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.