A bicycle made in China: the production specification must keep pace with component substitutions
Identify a proposed component change, send it for assessment and keep the production run, documents and customer-facing specifications aligned.
Article language: English

In this article
“We can supply a different part from the same brand.” A bicycle manufacturer may be making a reasonable proposal. The message does not yet identify the change, assess it or obtain agreement to use it in the agreed production run. A component logo is useful information. It should not replace the whole discussion about what is to leave the factory.
Imagine a Polish brand preparing a run of conventional city bicycles in China. The equipment list has been agreed and a pre-production sample inspected. Before further production, the factory proposes a different rear derailleur model. The brand must send the proposal for appropriate assessment and then keep the production run, documents and customer-facing offer aligned. The bicycle's name will remain the same, but its specification may no longer be identical.
From an agreed product to a particular production run
A Fuji-Ta response published in Shanghai Stock Exchange documentation describes, among other things, customer confirmation of trial production and the creation of a BOM, purchase orders and production instructions from an order. A BOM is the list of materials and parts needed to make a product. This is the company's account of connecting agreements with production for a specific order.
The passage illustrates a useful distinction between getting to know a manufacturer and agreeing your own run. A supplier may be able to make a particular family of bicycles, but the ordered product still has to be tied to a specific equipment specification. When researching the manufacturer, ask how it identifies the agreed product and communicates a proposed component change. The answer should concern the actual working arrangement, not just a statement of flexibility.
When choosing OEM or ODM in China (in Polish), you establish the division of work in creating the product. Here a further question arises: which version is to be made in this particular run? Whatever the working model, the brand needs to know what it agreed and which proposal needs a new decision. Several identically named documents left in a folder are not enough.
A component record should distinguish its manufacturer, model and variant. A group's trade name may be too broad. If the factory uses an additional internal code, retain its connection to the component supplier's designation. Otherwise the two sides may confirm different things under their own abbreviations, leaving the Polish brand unable to reconstruct what actually changed.
This does not mean turning a sales description into an engineering manual. It means passing the right information to someone prepared to assess it. A salesperson can ensure the proposal has a complete identifier, the scope of the run and manufacturer materials. A suitable specialist assesses the component's suitability, how elements work together and what checks are required. Similar names or appearance alone do not justify technical acceptance.
Membership of a product group does not settle compatibility
In its product lineup, Shimano says it presents recommended products for each category and that compatibility must be checked separately. A family catalogue and a document concerning permissible combinations therefore serve different purposes. For a proposed change, ask for material that addresses the question requiring assessment.
A separate Shimano compatibility information database separates topics including drivetrains, braking systems and combinations of groups of components. This documentation from a Japanese parts manufacturer can be used as a source for an appropriate assessment of a component proposed by a Chinese factory. It does not by itself confirm the complete bicycle ordered by the Polish brand.
In the example, “a different derailleur from the same brand” should therefore lead to an exact designation and information about the proposed change. The point is not to reject the proposal as a matter of principle. It is to make it possible to identify what would actually replace the original part and whether something else needs checking. The assessment may lead to further questions. Do not fill gaps in the answer with your own belief that the change looks small.
A similar identification problem arises with a fishing equipment model and its parts (in Polish). A shared product name may not identify the correct part for a particular build. In a production-run bicycle there is also the scope of the change: which variant, which order and from what point in production is it to apply? The information should make those questions answerable.
An “approval” needs an object
Follow a message intended for assessment. The factory identifies the original component and the proposed model, attaches the relevant description and states which part of the order the proposal concerns. The brand sends the material to the designated specialist. The case record retains what is still unresolved. Only then can a response address the specific change rather than a general willingness to keep working together.
Determine internally who communicates the assessment result and who confirms a change to the order's scope. They may be different people. The factory should know their roles. A polite “thank you for the information” from someone collecting data should not function as approval to introduce a new build. That employee also needs to know how to respond while assessment is pending.
Preserve the full meaning of the response. “We need further material,” “you may proceed to a specified check” and “we confirm the indicated change within this scope” lead to different actions. A company should name these states according to its own process. There is no need for a multi-page message policy. It is enough to prevent a substitution question from disappearing inside a thread confirming delivery dates.

This is also a boundary of a product sample assessment plan (in Polish). A pre-production example may represent the previously agreed version well. If a change is later proposed, establish its effect on the scope of the earlier assessment and further checks. A retained sample is not automatic evidence of the properties of every later build sold under the same name.
With several sizes or versions, check the proposal's boundaries carefully. Does the new part concern the entire order or a specified variant? Has part of the run already been made to the original specification? The information should distinguish those states. One shared folder name cannot be the only way to identify the bicycle the brand will later describe and support.
The factory's message may also say that some bicycles have already been prepared to the original list. In that case, adding the new component to one shared sheet is not enough. First establish which build the agreement covers and how to recognise it in the delivered run. The brand should receive that information in a form usable for subsequent support, not only as an oral assurance during a conversation.
The identification method must suit the product and process. Commercially, however, you need to know whether a particular customer received the earlier or the changed specification. If both builds are within one order, the order number alone may not distinguish them. Name that gap before the product is released for sale.
Documents must keep up with the build
The Shimano technical information site shows separate versions and dates for its materials: at the recorded check, compatibility information was version 2.7 dated 7 October 2026 and product lineups were version 2.6 dated 17 September. Retain such identifiers for the material used. Document currency and component identification are separate pieces of information needed to reconstruct the basis of an assessment.
After agreeing a change, compare the places where the brand describes the product. The production list, sales sheet and material given to the seller should concern the correct build. Changing a part name in one table is not enough if the old description still reaches the customer. Versioning a multilingual offer (in Polish) helps preserve the connection between an information change and its subsequent language versions.
A photograph has a specific role too. A picture of a pre-change sample may still illustrate its general shape, but should not be used without explanation as confirmation of the changed specification. If the brand publishes such material, it needs to decide how to show the correct scope and differences. A reader does not know the history of agreements with the factory and should not have to guess which parts of the image are outdated.
Keep the ability to return to the earlier build in the documentation. The point is not to put it back into production. It is to identify a product already with a customer. In supporting spare parts for an older series (in Polish), identifying what was previously delivered is precisely the starting point. Deleting the old specification would tidy the folder at the cost of that knowledge.
Also check what the seller who did not take part in the choice receives. “Change approved” may not be enough to answer a customer asking about equipment. The seller needs the correct description and its scope, without reconstructing factory correspondence independently. They should not add their own assessment that the new part is better if no basis for that was established.
If the proposal is rejected, retain that decision with the order. Establish what answer is expected next: confirmation that the original build is possible or another precisely described proposal. Refusing one substitute does not itself explain what the factory should do with the whole order. This part of the discussion should return to the person handling the case, rather than remaining only in technical documentation.
What to ask when researching a factory
Before requesting a quotation for the whole run, present the manufacturer with an example component change and ask how it would be reported. How does the company specify scope? What documentation does it provide for assessment? How does it distinguish waiting for an answer from confirmation? These questions help understand its ability to cooperate. A count of bicycles shown in a factory presentation cannot replace them.
Aeneia Oriens can help research available sources and Chinese manufacturers’ statements and prepare questions about specifications and production-run identification. Internal practices need confirmation with the manufacturer. The material can support a commercial discussion, but does not replace technical assessment or confirmation of requirements for the particular product.
An anonymised example notice makes useful material for a first discussion: the current part identifier, the proposed identifier, the specified scope and the missing confirmation. Ask the manufacturer who will complete the data on its side and how the information reaches the correct production order. You will then receive an account of the proposed-change process instead of a general assurance of good customer contact.
At the first change notice, check whether someone outside the correspondence can identify the old component, the proposal and the scope of the run. Can they see the assessment basis and decision status? Can they find the current sales description? If they must call the author of the message to establish what was actually agreed, the record needs completing. A well-managed conversation leaves more than a memory that everyone agreed on the brand.







