PHPackages                             inpost-vonhalsky/module-magento - 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. inpost-vonhalsky/module-magento

ActiveMagento2-module

inpost-vonhalsky/module-magento
===============================

VonHalsky integration module for Magento 2.4.x (PHP 8.1+)

1.0.1(1mo ago)275↑33.3%1[7 issues](https://github.com/InPost-VonHalsky/InPost-vonHalsky-Magento/issues)[3 PRs](https://github.com/InPost-VonHalsky/InPost-vonHalsky-Magento/pulls)OSL-3.0PHPPHP ^8.1

Since Jul 17Pushed 1mo agoCompare

[ Source](https://github.com/InPost-VonHalsky/InPost-vonHalsky-Magento)[ Packagist](https://packagist.org/packages/inpost-vonhalsky/module-magento)[ RSS](/packages/inpost-vonhalsky-module-magento/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (2)Dependencies (22)Versions (4)Used By (0)

VonHalsky Module for Magento 2.4.6–2.4.8 (PHP 8.1+)
===================================================

[](#vonhalsky-module-for-magento-246248-php-81)

> 🇵🇱 Polska wersja dla merchantów: [README.pl.md](./README.pl.md)

The VonHalsky module connects Magento 2 stores with InPost marketplace services. It synchronises offers, categories, orders, and related events while giving merchants intuitive admin tools to manage mappings and monitor activity.

> ✨ **Productization — the game-changer.** VonHalsky's standout feature reads product data straight from InPost's catalog by EAN (the `/hints` endpoint) and pre-fills the whole offer for you — category, attributes, brand and more. In practice this **removes the need to map categories or attributes by hand**: pick a product, review the pre-filled offer, and publish. Creating marketplace offers becomes genuinely fast and effortless.

> 📦 **Distribution.** The module is published on Packagist and installed with Composer — see [Installation](#installation).

Resource Menu
-------------

[](#resource-menu)

- [User Guide (Quick Start)](./doc/quick-start.md)
- [Installation](#installation)
- [Scheduled Cron Jobs](#scheduled-cron-jobs)
- [Admin &amp; CLI Operations](#admin--cli-operations)

Requirements
------------

[](#requirements)

- Magento Open Source / Adobe Commerce **2.4.6–2.4.8**
- PHP **8.1** or newer
- Composer 2.x
- Valid VonHalsky OAuth2 credentials (Client ID &amp; Client Secret)
- Working Magento cron and access to the Magento CLI (`bin/magento`)

Installation
------------

[](#installation)

The module is published on Packagist as `inpost-vonhalsky/module-magento`, together with its InPost PHP SDK. Installation is a standard `composer require` — no `repositories` configuration is needed.

> 📚 **Separate SDK repository.** The InPost PHP SDK is maintained in its own repository — [InPost-vonHalsky-api-sdk-php](https://github.com/InPost-VonHalsky/InPost-vonHalsky-api-sdk-php) (Packagist: `inpostapi/inpost-vonhalsky-api-sdk-php`). Composer pulls it in automatically as a dependency of the module; you do not install it separately.

### 1. Require the module

[](#1-require-the-module)

From the Magento root:

```
composer require inpost-vonhalsky/module-magento
```

Composer resolves the module and its dependencies (the InPost PHP SDK `inpostapi/inpost-vonhalsky-api-sdk-php` and `league/oauth2-client`) automatically from Packagist.

### 2. Enable the module and run setup

[](#2-enable-the-module-and-run-setup)

```
bin/magento module:enable Inpost_VonHalsky
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush
```

`bin/magento module:status Inpost_VonHalsky` should now list the module as enabled.

### 3. Upgrading to a new release

[](#3-upgrading-to-a-new-release)

```
composer update inpost-vonhalsky/module-magento
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush
```

Documentation
-------------

[](#documentation)

The complete user guide — setup, configuration, daily operations, and troubleshooting — lives in **[doc/quick-start.md](./doc/quick-start.md)**, with accompanying screenshots under `doc/screenshots/`. New merchants should start there and follow it in sequence.

Highlights
----------

[](#highlights)

- **OAuth2 Integration** – Secure token handling and automatic refresh via `OAuth2Service`.
- **Organization Management** – Retrieve and cache available organizations, with manual refresh controls.
- **Admin Experience** – Dedicated Magento menus for Offers, Category Mapping, and Orders; attribute mapping and event tracking are managed within those sections.
- **Category Search** – Search box above the InPost category tree in Category Mapping; partial match, case-insensitive, with breadcrumb path and highlighted results. Backed by a shared cache — zero DB queries after first load.
- **Bulk Synchronisation** – CLI commands for offers, categories, events, and orders, with filtering options (and dry-run where applicable).
- **Automation Ready** – Cron jobs schedule critical synchronisations automatically (see table below).
- **Robust Architecture** – Service-oriented code with comprehensive logging, validation, and error handling (`ApiErrorHandler`).

Shipping Automation (optional — Smartmage InPost)
-------------------------------------------------

[](#shipping-automation-optional--smartmage-inpost)

VonHalsky integrates with the **Smartmage\_Inpost** module (InPost Paczkomat / Courier shipping methods and ShipX parcel generation). This is a **soft dependency** — VonHalsky works fully on its own. When `Smartmage_Inpost` **is** installed, accepted marketplace orders can be mapped to InPost carriers and their **ShipX shipments (waybills / shipping labels) generated automatically** — so the entire order-to-shipment flow can run hands-free, with no manual label creation. Configure carrier mapping and automatic shipment creation under **Stores → Configuration → VonHalsky → Delivery Method Mapping**.

Scheduled Cron Jobs
-------------------

[](#scheduled-cron-jobs)

JobDefault SchedulePurposeCategories`0 2 * * *` (2 AM daily)Sync InPost categoriesEvents`*/15 * * * *` (every 15 min)Sync offer/order eventsOrders`*/10 * * * *` (every 10 min)Sync orders from InPostUpdated Offers`*/5 * * * *` (every 5 min)Re-send offers flagged for API syncPending Commands`*/3 * * * *` (every 3 min)Poll async create-offer commands; finalize/retryAll schedules are configurable in **Stores → Configuration → VonHalsky → Cron Settings**.

Admin &amp; CLI Operations
--------------------------

[](#admin--cli-operations)

- Configure credentials under **Stores → Configuration → VonHalsky → Configuration**. Use the provided action buttons to connect, test, and refresh organizations.
- Operate day-to-day workflows from the **VonHalsky** admin menu (Offers, Category Mapping, Orders).
- Run console commands such as `bin/magento inpost:categories:sync --clean` or `bin/magento inpost:offer:send --all` for manual control.

See the [User Guide](./doc/quick-start.md) for detailed instructions, options, and usage examples.

Support &amp; Maintenance
-------------------------

[](#support--maintenance)

- Logs are stored under `var/log`, including `inpost_debug.log` for module-specific diagnostics.
- Always clear Magento caches after configuration changes (`bin/magento cache:flush`).
- Consult the [User Guide](./doc/quick-start.md) for a troubleshooting checklist before escalating issues.

**Need help?** If you run into problems, contact InPost API support at ****. Include the module version, your Magento version, and relevant excerpts from `var/log/inpost_debug.log`.

---

*Module namespace: `Inpost_VonHalsky`*

###  Health Score

37

—

LowBetter than 81% of packages

Maintenance71

Regular maintenance activity

Popularity17

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity44

Maturing project, gaining track record

 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 ~2 days

Total

2

Last Release

43d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/302013253?v=4)[mbachsii](/maintainers/mbachsii)[@mbachsii](https://github.com/mbachsii)

---

Top Contributors

[![mbachsii](https://avatars.githubusercontent.com/u/302013253?v=4)](https://github.com/mbachsii "mbachsii (5 commits)")

###  Code Quality

Static AnalysisPHPStan, Rector

Code StylePHP CS Fixer

Type Coverage Yes

### Embed Badge

![Health badge](/badges/inpost-vonhalsky-module-magento/health.svg)

```
[![Health](https://phpackages.com/badges/inpost-vonhalsky-module-magento/health.svg)](https://phpackages.com/packages/inpost-vonhalsky-module-magento)
```

###  Alternatives

[mollie/magento2

Mollie Payment Module for Magento 2

1162.0M19](/packages/mollie-magento2)[run-as-root/magento2-prometheus-exporter

Magento2 Prometheus Exporter

68365.7k](/packages/run-as-root-magento2-prometheus-exporter)[loki/magento2-components

Core module for defining Alpine.js components with advanced AJAX features

1019.5k30](/packages/loki-magento2-components)[dotdigital/dotdigital-magento2-extension

Dotdigital for Magento 2

50413.8k28](/packages/dotdigital-dotdigital-magento2-extension)[yireo/magento2-emailtester2

Preview transactional emails and test send them in your backend

34452.5k](/packages/yireo-magento2-emailtester2)[buckaroo/magento2

Buckaroo Magento 2 extension

32431.3k8](/packages/buckaroo-magento2)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
