1C:Enterprise
This plugin usesIntegration Module
npm install @gorgo-store/medusa-erp-1c
Category
Built by
Version
unknown
Last updated
3 days ago
Monthly downloads
Loading downloads
Github stars
0
Closed beta of the paid version
The paid version pushes orders back into 1C and adds per-warehouse stock and price types.
Apply for the betaMedusa – 1C:Enterprise Integration
Documentation
Two-way exchange of the catalog, prices, stock and orders between Medusa and 1C:Enterprise.
Читать README на русском ↗
Paid plugin for data exchange between Medusa and 1C:Enterprise ERP over the CommerceML protocol. The free version, 1C:Enterprise Catalog, only imports the catalog and prices.
The plugin is in closed beta. Participants get a price below the release one for the first year, help with the edge cases of their own 1C configuration and a chat with the development team. To take part in the testing, apply for the beta.
Plugin Features
- Catalog from 1C – products, categories from classifier groups, product types and images.
- Offers – variants with SKUs, options built from characteristics, and the retail price.
- Price types – every non-retail 1C price type becomes a Medusa price list.
- Per-warehouse stock – 1C warehouses become Medusa stock locations, with stock levels kept for each.
- Two-way order exchange – Medusa orders go to 1C, and orders created in 1C come into Medusa.
- Catalog export to 1C – products created or changed in Medusa go to 1C.
- Products missing from 1C – after a full catalog export, you can unpublish or delete them.
- Large catalogs – the plugin is tested on a 400,000 SKU catalog and processes it in batches of 100 products.
- Workflow hooks – your own code adjusts what the exchange writes to Medusa and sends to 1C, without forking the plugin.
- Integration Module – you configure every plugin setting in the Medusa Admin, with no edits and no redeploy.
💬 Support & Community
Got questions or ideas about the plugin? Join the Telegram support chat, @gorgojs_chat.
Connect with other Medusa developers on Telegram, @medusajs_chat.
Requirements
- Medusa server v2.17.2 or later
- Node.js v20 or later
- Integration Module v0.1.4 or later
- An access token for Gorgo's package registry
Installation
packages are published to the registry, not to the public npm registry. You get an access token for it once your beta application is approved. Point your package manager at this registry for the scope and pass it the token. Yarn 2 and later reads its settings from :
npm reads them from :
Both files take the token from the environment variable, so it stays out of your project's repository. Set it wherever dependencies get installed, on your machine and in CI. Then install the plugin together with the Integration Module:
Documentation
The getting started guide covers registering the plugin in , the database migrations and setting up the exchange in 1C. The settings in the Medusa Admin, the workflow hooks and everything else are on the Gorgo documentation website.
License
Commercial software sold by subscription. Each version released during your paid period stays yours for good, and the subscription covers new versions. The terms are set out in the License Agreement in the package's file.