1C / BAS integration with MODX - data exchange built for your specific site setup
MODX is rarely “standard” – every site is built for specific needs, so we build the exchange with 1C or BAS around your resource structure and TV parameters, not a generic template.
MODX is almost always a custom build, and the data exchange needs to match that
Unlike WordPress or OpenCart, where off-the-shelf solutions exist, MODX sites are usually built individually: their own resource structure, their own TV parameters, and often custom catalog logic through MIGX or other add-ons. That means a ready-made “universal” 1C exchange module rarely works here, we have to look at the specific site implementation before proposing a solution.
That’s not a flaw, it’s a feature of the platform: the same flexibility that let you build the site exactly the way you needed requires the same individual approach when it comes to exchanging data with the accounting system.
What we can sync
Product catalog and resources
Products are exported from 1C/BAS into the MODX resource structure, matching how your catalog is actually organized, through standard resources, MIGX, or another approach.
TV parameters and attributes
1C fields are mapped to resource TV parameters, so price, stock, SKU, and other attributes land exactly where they're used on the site.
Stock and prices
Regular updates of stock and prices from the accounting system, on a schedule or on a trigger, depending on your site's load.
Orders back into 1C/BAS
If the site has an order form or cart, we set up order data flowing into the accounting system with no manual transfer.
Customization for non-standard scenarios
If your site's catalog logic is non-standard, we build the exchange specifically for your structure, rather than trying to force a generic solution to fit.
The order of work
Before proposing a specific solution, we look at your site’s implementation: which MODX version, how the resource structure is organized, whether TV parameters and add-ons like MIGX are used for the catalog.
Based on that review, we put together a technical spec for the exchange, confirm it with you, and only then configure the sync itself and test it on your real catalog data, the only reliable way to confirm the exchange works correctly with your specific build, rather than with an average idea of how MODX sites are “usually” set up.
Why this is our approach
We specialize in the 1C/BAS ecosystem, and most of our integrations are exactly this kind of "non-standard" case, where no off-the-shelf solution exists: the client's platform is specific, the data structure is individual, and the business processes don't fit a typical scenario.
MODX is just another one of the dozens of non-standard integrations we've already built: we review your specific implementation first, and only then propose a solution, not the other way around.
FAQ 1C\BAS | MODX
Describe how your catalog is organized (standard resources, MIGX, or otherwise) and which 1C/BAS configuration you use, we’ll suggest an approach for your specific case.
1C/BAS integration with MODX: data exchange built for a custom site structure
MODX sites are rarely “standard” – each one is built for specific needs, with its own resource structure and TV parameters. That’s why a ready-made universal exchange module with 1C or BAS rarely works here, and a 1C MODX integration always starts with reviewing the specific site implementation.
What a 1C MODX data exchange involves
Depending on your site’s structure, the exchange covers the product catalog, TV parameters (price, stock, SKU), stock and prices, and orders if the site has a cart or order form. If the catalog is built through MIGX or another add-on, that’s factored into the exchange design, it’s important to understand exactly how the structure is built before proposing a solution.
Why a standard module doesn’t fit here
The flexibility of MODX, which lets you build a site around specific business requirements, means the exchange with the accounting system needs to be just as custom. We don’t try to force a universal solution onto a non-standard structure, instead, we build an exchange that matches your actual site implementation.
If you want to understand the scope of work for integrating your specific MODX site, describe your catalog structure and 1C/BAS configuration in the inquiry on this page.