MerchandiserOS

ERP guide/Corrections

ERP implementation guide · textile & apparel

Corrections Policy and Changelog

This guide is only useful if it is right. This page explains how to tell us when it is not, how we source and check what we write, how often we re-check it, and what has changed since it was first published.

Applies to every page of the ERP guide Last checked 26 Sep 2026 Published by MerchandiserOS
Who wrote this. The ERP guide is published by MerchandiserOS, an operations platform for garment factories, fashion brands and buying agents that connects to ERPs through a public API and integrates with Garment.io. We are not affiliated with any ERP vendor. See the full disclosure.

1How do I report a correction to the ERP guide?

Send it through the contact form at merchandiseros.online/#get, and mention the page and the version you checked. A good report names three things, and we can act on it fastest when it has all three.

  • The page and the statement. For example, "NetSuite chapter, the section on matrix items, the sentence about the 2,000 limit".
  • The version you checked. The ERP version, edition or release wave, because many statements are true for one version and not the next.
  • What you found. A link to the vendor's documentation, a release note, or a description of what the product did on your system.

We welcome corrections from ERP vendors and their partners as much as from users. A correction is judged on its evidence, not on who sends it.

2How are the claims in the guide sourced?

Every product-specific claim in the guide cites the vendor's own documentation and names the version it was checked against; where a claim rests on a partner or third-party page, the source list says so; and where we could not confirm a capability, the text says "check your version" or marks the cell "check" rather than guessing.

  • Vendor facts come from official documentation, release plans and knowledge-base articles, listed at the end of each chapter and on the comparison page.
  • Practitioner judgement, such as a typical hypercare length or which ERPs a mid-size brand usually shortlists, is labelled as judgement and never presented as measured fact.
  • No invented numbers. The guide quotes no industry failure rates, market shares or implementation durations without a primary source. Prices in the worked examples are illustrative and say so.
  • Worked examples follow one order of 3,000 polos across every page, and every figure is shown with its arithmetic so a reader can re-check it.

3What happens after a correction is reported?

We check the report against the vendor's documentation or by reproducing it, correct the page if the report holds, and add a dated line to the changelog below. If the evidence is unclear, we change the statement to "check your version" until it is confirmed either way.

  1. We read the evidence.
  2. We check it against the current documentation for the version named.
  3. If the statement is wrong, we correct it; if it depends on the version, we name the versions; if it cannot be confirmed, we mark it "check".
  4. We record the change, with its date, in the changelog.

4How often is the guide re-checked?

Every chapter is re-checked at least once a year, and after each major release of the ERP it covers. The "Last checked" date at the top of every page shows when that page was last verified, and the comparison page and the hub are re-checked whenever a chapter changes a fact they summarise.

Changes that break integrations, such as a deprecated API or an authentication method being retired, are checked as soon as the vendor announces them. Odoo 19's deprecation of XML-RPC and NetSuite's retirement of token-based authentication for new integrations are two current examples the chapters already track.

5Changelog

Every change to a fact in the guide is dated here, newest first. Changes to wording that do not change a fact are not listed.

6Who publishes the guide, and what are its ties to vendors?

MerchandiserOS publishes this guide. MerchandiserOS is an operations platform for garment factories, fashion brands and buying agents: it runs style and tech pack, costing, orders, procurement, planning, production, the shop floor, quality and logistics, and connects to ERPs, which keep the books, through a file exchange or a public ERP API.

  • No vendor ties. MerchandiserOS is not affiliated with, and does not resell, any ERP named in the guide. No vendor paid for, reviewed or approved any page.
  • Garment.io. MerchandiserOS integrates with Garment.io, a shop-floor system, and the guide names it for that reason. The guide is not endorsed by Garment.io.
  • Our own interest. The guide recommends running operations in a system built for apparel on top of the ERP, and MerchandiserOS is such a system. We say so wherever the recommendation appears, and every ERP chapter also explains how to do the work inside the ERP for readers who choose that route.
  • Trademarks. Product names are trademarks of their owners and are used only to name the products. The guide uses no vendor logos and makes no claim of partnership, certification or official status.
Report a correction Back to the guide