Behind a c-store pricebook that stays current is usually a data standard called NAXML. It is the common language that lets a store, its POS, and its suppliers exchange item, price, and promotion data without every system speaking its own dialect. You rarely see it, but it carries a lot of the load.
What NAXML is
NAXML, short for NACS eXtensible Markup Language, is an open, non-proprietary data standard for the convenience store and petroleum industry. It defines a shared format for exchanging business data: items, prices, promotions, invoices. With a common format, a retailer's POS, back office, and suppliers can pass data back and forth cleanly instead of fighting incompatible files.
Where it came from
It grew out of the National Association of Convenience Stores' technology standards effort, then was carried forward by PCATS, the Petroleum Convenience Alliance for Technology Standards, founded in 2003. PCATS built the XML-based standards known as PCATS-NAXML, and those standards are maintained today by Conexxus, the industry's standards organization.
The documents it moves
NAXML is a set of named XML documents, each with a fixed schema. In the POS/Back Office standard, maintenance documents push setup data down to the register and movement documents pull results back. The ones an operator meets most often:
- ItemMaintenance: item-level data the back office sends to the POS so the register can sell the item at the right price.
- PromotionsMaintenance: mix-and-match and combo deal definitions.
- POSJournal: a transaction-by-transaction log of everything the register rang.
- ItemSalesMovement: summarized item sales for a period, the raw material for reporting and reordering.
- FuelGradeMovement and TankProductMovement: fuel sales by grade and tank-level product data from the forecourt.
One price change, start to finish
Say your cigarette wholesaler raises carton costs on a Monday. The new costs land in your back office as item data. Your pricebook applies your margin rules, and the back office sends an ItemMaintenance document to every register. By the afternoon, each POS rings the new price. That night, POSJournal and ItemSalesMovement come back, so Tuesday's report shows exactly how the change sold. Nobody typed a price at a register. That round trip is what breaks when item and cost data gets hand-keyed instead, and it is the flow FastDragon C-store is built around: standardized data in, current prices and honest margins out. Clean transaction detail from that same loop also feeds scan data reporting.
NAXML and EDI
NAXML and EDI solve the same basic problem of system-to-system exchange. NAXML files are XML, plain text a person can open and read, and the standard was designed to cost less to implement than traditional EDI. Fuel-side paperwork still runs on EDI in many places: jobber and fuel marketer software often trades invoices and bills of lading with suppliers that way. A modern back office may need to speak both.
Answers to common questions
Do I need to buy or license anything to use NAXML?
No. The schemas are published by Conexxus and free to implement. What you pay for is software that supports them, so the useful question for any POS or back-office vendor is which document types they can import and export, and in which versions.
Which NAXML version should I ask my vendor about?
Conexxus describes version 3.4 of the POS/Back Office standard as the most widely deployed release. Newer releases run through 3.7, and a 4.0 revision with JSON and API support is planned. Versions change, so confirm the current release on the Conexxus site before writing one into a contract.
Can my POS and back office come from different vendors?
Yes. Letting retailers pick each system on its merits, and still have the two trade data, was a founding goal of the POS/Back Office standard. Ask both vendors which document types and versions they support, since partial implementations are common.
Does tobacco scan data reporting use NAXML?
The manufacturer programs each define their own weekly file formats; an Altria submission is structured differently from an RJ Reynolds one. Back-office software builds those files from the transaction detail the register already exports, so a store with working POS-to-back-office data exchange has a much easier path into scan data programs.
Is NAXML the same thing as Conexxus?
Conexxus is the membership organization that writes technology standards for convenience and fuel retailing. NAXML is one family within that work, alongside standards for payments, loyalty, and device integration. If a vendor says they are "Conexxus compliant," ask which specific standards and documents they mean.