Serial-range fitment
Each application carries its serial range from the source catalog.
- A break with no exact serial is flagged for counter confirmation
- Built during implementation
Uncap builds tractor and implement parts B2B ecommerce on Shopify for all-makes parts distributors, equipment dealers and implement manufacturers selling to farms, repair shops and other dealers. Three things set this trade apart. The right part can change partway through a model's production run, so the model number gets you close and the serial number decides. An implement only works if its hitch category and PTO shaft match the tractor it goes behind. And in planting and harvest, a planter or combine that is down can make the nearest branch with the part worth more than the lowest price.
The model number gets you close, the serial number gets you the part, and an implement has to match the tractor it goes behind.
The model number gets you close. The serial number gets you the part. A manufacturer can change a component partway through a production run, and its parts catalog records the change against serial numbers. One John Deere tractor parts catalog explains its own notation: "Serial number information is listed to show on which machines each part can be used." A serial number followed by a dash means the part fits machines "beginning with the serial number listed." A dash followed by a serial number means "up to and including the serial number listed." Two tractors of the same model can take different parts, and a storefront that filters by model alone shows both.
Some breaks are printed before the exact serial is available. The same catalog says: "When XXXXXX's are listed in place of a serial number, a serial number change was made, but the exact serial number was not available at the time of publication." Your counter handles that by asking for the serial plate. A website needs the same confirmation step, not a confident add to cart.
All-makes catalogs inherit breaks from many brands. An OEM dealer sells one maker's genuine parts against that maker's catalog. An all-makes distributor sells aftermarket parts cross-referenced to several makers' numbers. Each cross-reference has to carry the original serial range with it, or an aftermarket water pump shows as fitting tractors it does not fit.
Hitch category is a fit question, and horsepower does not settle it. ISO 730 defines the rear three-point linkage in eight categories: 1N, 1, 2N, 2, 3N, 3, 4N and 4. India's IS 4468 (Part 1):1997, a national standard revised to align with ISO 730-1, ties each of its four categories to a band of PTO power: Category 1 up to 48 kW, Category 2 up to 92 kW, Category 3 at 80 to 185 kW and Category 4 at 150 to 350 kW. The bands overlap: a tractor making 85 kW at the PTO sits inside both Category 2 and Category 3, so the category belongs on the tractor record, not in a horsepower rule. IS 4468 also requires that the design of the lower links, or double-ended hitch attachments, let a Category 1 implement be fitted to a Category 2 linkage or the reverse, and the same for Categories 2 and 3. That hardware is a line on the order if the storefront knows to offer it. The same standard defines a three-point hitch coupler, what the trade sells as a quick hitch, as a "Device which facilitates the connection of the tractor three-point linkage to the implement."
PTO speed and spline count are on the shaft, not on the product page. A 2013 ASABE Distinguished Lecture on tractor power for implement operation tabulates the rear PTO shafts in ISO 500-1 as it stood then. Type 1 is a 35 mm shaft with 6 straight splines at 540 rpm, or at 1000 rpm in Europe. Type 2 is a 35 mm shaft with 21 involute splines at 1000 rpm. Type 3 is a 45 mm shaft with 20 involute splines at 1000 rpm. The lecture adds: "Only the 540 rpm, 6 spline shafts are allowed in North America." So in North America, a buyer counting splines on a stub shaft is telling you the speed, and the shaft belongs on the machine record next to the serial number and hitch category.
In the window, the nearest branch can beat the lowest price. A combine down in October or a planter down in April is rarely a comparison shopping moment. The service tech next to the machine wants three answers. Which branch has the part on the shelf right now? Can it go on a truck today? What does overnight freight cost if neither works? Price often comes fourth. A site that shows one network-wide stock number sends that buyer to the phone, in the weeks your counter has the least time to answer it.
Serial-break resolution, hitch and PTO compatibility, saved machines and branch-first availability are built during implementation from your data.
Serial ranges on every application, checked before the cart. Each fitment record carries the serial range from the source catalog: from a serial, up to a serial, or between two. The buyer enters a serial number or picks a saved machine, and sees only the parts whose range includes it. A break the catalog marks as unknown goes to your counter instead of being guessed. Serial-break resolution and saved machines per account are built during implementation from your OEM catalogs and cross-reference data. That matches the machinery and equipment page, where serial-to-build resolution is an extension built on Uncap Diagrams, not a shipped feature.
Hitch and PTO checked like any other fit. The tractor record holds its hitch category and its PTO type. The implement record holds what it needs. When a buyer adds a rotary cutter or a tiller, the storefront checks both against the selected tractor. A Category 1 implement on a Category 2 tractor gets the hitch hardware offered alongside. A 1000 rpm driveline headed for a 540-only tractor gets a warning before checkout, not a return after. These rules are built during implementation from your catalog and machine data.
Branch stock the buyer can drive to. Shopify tracks inventory separately at each location and supports pickup in store per location, so each branch set up as a location can ship or hand over an order. Uncap Connect keeps Shopify and your ERP in real-time, two-way sync of inventory, orders, customers and pricing. Branch-first availability, showing the buyer's home branch, then the nearest branches, with a same-day pickup or truck cutoff, is built during implementation on inventory synced through Uncap Connect.
On whether an ERP-native platform shows branch stock more reliably. The case for a platform built on the ERP is that it reads stock directly. Uncap's published products do not include serial-break, hitch or PTO logic; on Shopify that layer is built during implementation from your data. The real risk on Shopify is an integration that does not carry B2B accounts, pricing and stock through correctly. Integration runs through an owned Uncap Connect app embedded in Shopify, or a managed iPaaS integration. On the Connect route there is no separate middleware: Connect syncs "customer-specific pricing, credit terms, and tax rules," and keeps the ERP as the system of record.
Exceptions go to a person, with the clock running. An unknown serial break, overnight freight on a heavy gearbox or a special order from the OEM should not be self-serve. Uncap Quotes runs configure, price, quote inside the Shopify admin, with negotiated prices, tiers and volume breaks applied automatically. It sends exceptions to the right approver, keeps validity windows on quotes, and turns an approved quote straight into a Shopify order. Hot-shot delivery to the field can be a line on that order, because Uncap Portal lets a Shopify store sell services alongside standard ecommerce products.
Every account sees its own prices, reorders and limits. In Uncap Portal, farms, repair shops and sub-dealers get real multi-user accounts with roles and permissions, and each buyer sees their assortment and pricing. Filters, belts and wear parts sit on reorder lists. Budgets, approvals and limits per user let a farm manager decide what a hired hand can put on the account, and NET terms, invoices and payments sit in the portal.
Proof, labeled at its true distance. Uncap has not published a tractor or implement parts case study. The closest is an agriculture build: Farmers Depot runs Shopify Plus B2B with Microsoft Dynamics 365 Finance and Operations as the system of record. It serves 14,528 customers buying under company accounts across 13,046 companies, with about 10 company-specific pricing catalogs, and APPSeCONNECT middleware handles the two-way sync. It shows account pricing at agricultural scale, not serial-break, hitch or PTO logic.
Account pricing, quote approvals, one-click order conversion, reorder lists and per-user limits ship in Uncap Quotes and Uncap Portal, and the fit logic is built during implementation from your data.
Each application carries its serial range from the source catalog.
The implement's category is checked against the tractor's, with hitch hardware offered where one category can be fitted to another.
The implement driveline's speed and spline are checked against the tractor's PTO before checkout.
Stock at the buyer's home branch and nearest branches, with pickup by location and each branch's truck cutoff.
Unknown breaks, expedited freight and special orders routed through Uncap Quotes and converted to a Shopify order in one click.
Pricing, inventory, customers and orders kept current between Shopify and the ERP.
Serial-range fitment. Each application carries its serial range from the source catalog, and a break with no exact serial is flagged for counter confirmation instead of sold as a sure fit, built during implementation.
Hitch category check. The implement's category is checked against the tractor's, with hitch hardware offered where one category can be fitted to another, built during implementation.
PTO type check. The implement driveline's speed and spline are checked against the tractor's PTO before checkout, built during implementation.
Branch-first availability. Stock at the buyer's home branch and nearest branches, with pickup by location and each branch's truck cutoff, built during implementation on inventory synced through Uncap Connect.
Exception quotes with approvals. Unknown breaks, expedited freight and special orders routed through Uncap Quotes, with the routing rules configured during implementation, and converted to a Shopify order in one click.
ERP sync, Connect or managed iPaaS. Pricing, inventory, customers and orders kept current between Shopify and the ERP, through an owned Uncap Connect app embedded in Shopify, or a managed iPaaS integration.
The line between product and build, in writing. Account pricing, quote approvals, one-click order conversion, reorder lists and per-user limits ship in Uncap Quotes and Uncap Portal. Serial-break resolution, hitch and PTO compatibility, saved machines and branch-first availability are built during implementation from your data. The scope says which is which.
Credentials you can check. Uncap is a Shopify Platinum Partner, on Shopify since 2013, with 380+ unified storefronts launched on Shopify.
Scoped before it is built. The Uncap Blueprint is a fixed-price, four-week Shopify migration plan, credited 1:1 toward implementation. It covers solution architecture, a data migration taxonomy, an ERP integration audit, UX and flow prototyping, total cost of ownership and a risk register, and ends with a fixed-cost implementation estimate. For a parts distributor, that architecture work can cover serial ranges, hitch and PTO data, branch inventory and the ERP integration. You walk with everything you need to brief any agency or your in-house team.
This page sits under agriculture and farm supply ecommerce, which covers the season, grower pricing, pre-season programs and credit with the settlement that comes months later. This page goes one level down, into the checks a tractor or implement part has to pass before it ships. Diagram ordering, where a buyer clicks the part off an exploded view with fitment by model, year and assembly, is covered on machinery and equipment parts, and this page does not repeat it. If the same branches sell pivot parts and pumps, see irrigation and water systems. For how farm equipment fitment data gets assembled, see the field notes on selling tractor and implement parts online. For the ERP side, see the Dynamics 365 Business Central integration, the Dynamics 365 Finance and Operations integration, or the full list of ERP integrations.
Bring two documents. The first is a catalog page for your best-selling tractor model with its serial breaks on it. The second is a branch stock report from the busiest week of last harvest. Together they show how many parts change at a serial number, and how often the part sat in a branch the buyer could have reached.
Book a strategy session with Uncap, or start with a Blueprint if what you need first is the serial, hitch and branch logic written down and costed.
Not necessarily. On Shopify, serial-break, hitch and PTO logic is built during implementation from your catalog data, so the question is how directly the storefront reads stock by branch. On Shopify, inventory is tracked per location. Integration runs through an owned Uncap Connect app embedded in Shopify, or a managed iPaaS integration. On the Connect route, inventory, orders, customers and pricing stay in real-time, two-way sync with no separate middleware to maintain. Branch-first availability is built during implementation on that synced inventory, and Business Central stays the system of record.
A serial number break is the point in a production run where a manufacturer changed a part, so machines before and after that serial number take different parts. John Deere's parts catalog, for one, records it on each part as a serial range: from a serial number, up to one, or between two. Where the exact serial was not available at publication, that catalog prints XXXXXX, and a storefront should send those to a person.
They are linkage sizes with different dimensions for different ranges of tractors, defined in the international standard ISO 730 alongside Categories 1N, 2N, 3N, 3, 4N and 4. India's IS 4468 (Part 1), aligned with ISO 730-1, sets Category 1 for tractors up to 48 kW of PTO power and Category 2 up to 92 kW. Because the Category 2 band overlaps Category 3 (80 to 185 kW), check the operator's manual or measure the linkage instead of inferring the category from horsepower.
They are the speeds of the Type 1 to 3 rear PTO shafts in ISO 500-1 as tabulated in a 2013 ASABE Distinguished Lecture, and in North America the spline count tells you which one a tractor has. A 35 mm shaft with 21 involute splines and a 45 mm shaft with 20 involute splines run at 1000 rpm. A 35 mm shaft with 6 straight splines runs at 540 rpm, or at 1000 rpm in Europe; the lecture states that "Only the 540 rpm, 6 spline shafts are allowed in North America." The current edition, ISO 500-1:2014, also covers a Type 4 shaft.
It should show where the part is today, not only whether you stock it. Branch-first availability, pickup at the branch and same-day truck cutoffs are built during implementation on inventory synced through Uncap Connect. An order that needs a person, such as a special freight run, goes through Uncap Quotes to the right approver and converts to a Shopify order once approved.
Uncap publishes twelve ERP family integrations: Acumatica, Cin7, Epicor, Fishbowl, Infor, Microsoft Dynamics, NetSuite, Odoo, Oracle, QuickBooks, Sage and SAP. Pages that fit farm parts distributors include Dynamics 365 Business Central and Finance and Operations. Integrations are delivered through an owned Uncap Connect app or a managed iPaaS integration. For a dealer business system that is not on that list, the Uncap team confirms fit directly before anything is promised.
The machinery and equipment page covers finding a part from the machine by clicking an exploded diagram: fitment by model, year and assembly, assembly trees, diagram import and dealer pricing. This page covers what farm equipment adds: the serial number break inside a model, hitch category and PTO fit between tractor and implement, and branch stock when a machine is down in season. Many ag parts businesses need both.