Installation
Install mageb2b/onestepcheckout with Composer, then enable the Magento module and apply the normal deployment steps for the target mode.
Requirements
- Magento 2.4
- PHP 8.1 or a compatible newer PHP 8 release supported by your Magento installation
- Composer access to the SoftwareSilo package repository
Install with Composer
Use the SoftwareSilo Composer repository configured for your project. Keep the repository credential outside the project files.
composer require mageb2b/onestepcheckout:*
php bin/magento module:enable MageB2B_ExtensionManager MageB2B_OneStepCheckout
php bin/magento setup:upgrade
Production-mode deployments normally also require:
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:flush
Use the same release process and deployment options as the rest of the Magento installation.
Verify the module
php bin/magento module:status MageB2B_OneStepCheckout
The module must be enabled before the One Step Checkout configuration appears under Stores > Configuration > MageB2B. Open the configuration at the intended website or store-view scope and save only after reviewing the defaults.
First checks
Use a staging customer and a simple physical product to verify the complete flow:
- Open the cart and follow the checkout link.
- Confirm that shipping, payment and the order summary are visible on the same page.
- Enter a valid address and select a method offered by Magento.
- Place the order with the store's normal test payment method.
- Open the resulting order in Admin and confirm that the checkout still uses the expected Magento totals and methods.
The extension does not replace the carrier or payment configuration. A method that Magento rejects remains unavailable in this checkout.
Uninstall
php bin/magento module:uninstall MageB2B_OneStepCheckout runs the shipped uninstaller. It deletes all onestepcheckout/% rows from core_config_data, removes the onestepcheckout_cart_recovery cron schedules and drops the module's columns on quote, sales_order and sales_order_grid. Existing orders keep their rows but lose the order_comment and delivery_date values. The quote_address.osc_delivery_date column used by multi-address checkout is not removed by the uninstaller.
Next step
Continue with Configuration.
If the active storefront uses Hyva, install the Hyva Compatibility Add-On after the base package. The base module remains responsible for configuration, persistence and checkout rules.