When Malaysian Buyers Send "Preliminary Approval" for Custom Reusable Bags Without Clarifying Production Setup Authorization

Most procurement teams understand that approval is a formal milestone—a clear yes or no that determines whether production proceeds. In practice, this is often where customization process decisions start to be misjudged. The moment a buyer sends an email containing phrases like "preliminary approval looks good" or "approval in principle, pending final review," they believe they're helping the factory prepare efficiently. What they don't realize is that this language creates a binary interpretation problem. The buyer sees preliminary approval as a non-binding signal that formal approval will follow. The factory sees it as a commitment with formality pending—a green light to start production setup.

This trap manifests most clearly in a scenario that plays out across Malaysian corporate procurement every quarter. A marketing team reviews custom reusable bag samples and sends an email to the factory stating, "The design looks great. We're giving preliminary approval so you can start preparing. We'll send formal sign-off once legal reviews the compliance documentation." The procurement manager believes this message accomplishes two goals: it signals approval direction to keep the project moving, and it preserves the option to reject if legal finds issues. The factory project manager reads the same email and interprets it as authorization to order printing plates, procure materials, and allocate production capacity.

Figure 1: How buyers and factories interpret the same "preliminary approval" message differently, leading to RM 30,000-50,000 cost disputes

Three weeks later, the legal team flags a compliance issue with the product labeling. The marketing team requests a design modification and expects the factory to accommodate it without cost impact, reasoning that "we only gave preliminary approval, not final approval." The factory responds with a quote for RM 42,000 in sunk costs—printing plates already manufactured, materials already cut, production slots already reserved. The procurement team is shocked. From their perspective, preliminary approval explicitly communicated that formal approval was still pending. From the factory's perspective, preliminary approval was a commitment to proceed, with formal documentation being an administrative formality rather than a substantive decision gate.

The cost structure reveals why factories interpret preliminary approval as a production trigger. Custom reusable bag manufacturing operates on tight margins with long lead times for tooling and materials. When a factory receives preliminary approval, they face a choice: wait for formal approval and risk missing the delivery deadline, or start setup immediately and risk absorbing costs if approval fails. Factories that consistently wait for formal approval develop reputations for slow turnaround and lose business to competitors who start setup earlier. Factories that start setup on preliminary approval occasionally absorb sunk costs, but more often, buyers accept the costs because rejecting the order would delay their project by six to eight weeks. Over time, factories learn that preliminary approval functions as a de facto production trigger, even when buyers frame it as non-binding.

The timeline impact compounds the cost issue. Printing plate manufacturing takes seven to ten days. Material procurement from specialized suppliers takes fourteen to twenty-one days. Production capacity allocation happens weeks in advance, especially during peak seasons when factories operate at ninety percent utilization. When a factory receives preliminary approval, waiting for formal approval means adding three to four weeks to the delivery timeline. For buyers working against fixed event dates or product launch deadlines, this delay is often unacceptable. The factory's decision to start setup on preliminary approval isn't reckless optimism—it's a calculated response to the structural reality that buyers need speed more than they need optionality.

Malaysian buyers fall into this trap because they optimize for internal process requirements without considering how factories interpret approval signals. Corporate governance structures often require multiple sign-offs—marketing approves the design, finance approves the budget, legal approves compliance, operations approves logistics. Buyers want to keep the factory engaged throughout this process, so they send preliminary approval to signal that the project is progressing. They assume the factory understands that preliminary means "not yet final." But factories don't have visibility into the buyer's internal approval workflow. They see an email from the procurement contact stating "approval looks good" and interpret it as authorization to proceed. The word "preliminary" doesn't register as a substantive constraint—it reads as a formality descriptor, like "interim" or "provisional," indicating that paperwork is still being processed but the decision has been made.

The judgment error stems from treating approval language as universally understood rather than contextually interpreted. Buyers assume that "preliminary approval" clearly communicates "not yet binding." Factories interpret "preliminary approval" as "binding, with formalities pending." Both interpretations are reasonable within their respective operational contexts. Buyers operate in environments where approvals cascade through multiple stakeholders, and preliminary approval signals progress without foreclosing options. Factories operate in environments where production setup requires weeks of lead time, and any approval signal that isn't an explicit "do not proceed" is treated as authorization to start.

Some buyers attempt to clarify their intent by adding explicit language like "please wait for formal approval before starting production." This approach creates a different problem. Factories that strictly follow this instruction deliver products weeks later than competitors who start setup on preliminary approval. Buyers who initially insisted on waiting for formal approval before production setup often switch to factories that start earlier, because timeline pressure overrides process discipline. The market selects for factories that interpret preliminary approval as a production trigger, even when buyers explicitly request otherwise.

The preliminary approval trap also intersects with risk allocation structures. When a buyer sends preliminary approval and the factory starts setup, the question of who bears the cost if approval fails becomes ambiguous. The buyer argues that preliminary approval explicitly communicated non-binding intent, so the factory assumed the risk by starting early. The factory argues that preliminary approval signaled commitment, and the buyer's subsequent rejection represents a change of mind rather than a failure to approve. Neither party is being unreasonable—they're operating from different assumptions about what preliminary approval means. The ambiguity creates a negotiation over who absorbs the RM 30,000 to RM 50,000 in sunk costs, and this negotiation damages the relationship regardless of how it resolves.

Factories rarely push back on preliminary approval language during the initial communication because challenging it creates friction and delays the project start. Explaining that preliminary approval will be treated as a production trigger requires the factory to educate the buyer about manufacturing lead times, tooling costs, and capacity allocation constraints. This education process makes the factory appear difficult to work with, especially when competing suppliers simply accept preliminary approval without raising concerns. The factory's optimal strategy is to accept preliminary approval, start production setup, and address cost allocation only if approval fails. This reactive approach protects the factory's competitive position, but it doesn't prevent the underlying problem.

Figure 2: Decision framework for buyers to avoid preliminary approval traps by clarifying cost liability and timeline impact before communicating with factories

The solution requires changing how buyers communicate approval status during the internal review process. Instead of sending preliminary approval to keep the factory engaged, procurement teams need to recognize that any approval signal—regardless of qualifying language—will be interpreted as authorization to proceed. If the buyer genuinely wants the factory to wait, the communication should state "design review is progressing, but please do not start production setup until you receive explicit authorization." If the buyer wants the factory to start setup to preserve timeline, the communication should acknowledge that preliminary approval authorizes production preparation and that the buyer accepts cost liability if formal approval fails.

For organizations that cannot accept cost liability for preliminary approval, the alternative is to extend the delivery timeline to accommodate waiting for formal approval before production setup begins. This acceptance needs to happen at the project planning stage, not when the factory quotes lead time. Procurement teams should add three to four weeks to the baseline timeline if they plan to require formal approval before setup. This buffer accounts for the sequential nature of approval-then-setup rather than the parallel approach of approval-during-setup.

The preliminary approval trap reveals a broader pattern in customization process decisions: buyers communicate in ways that make sense within their internal processes without considering how those communications will be interpreted by external suppliers operating under different constraints. They use "preliminary approval" because it accurately describes the status within their organization—approval has been given by some stakeholders but not all. They don't realize that factories interpret approval status based on production implications, not organizational formalities. The word "preliminary" doesn't change the factory's decision calculus because the alternative—waiting for formal approval—creates timeline delays that buyers consistently reject.

Malaysian procurement teams that understand this dynamic build approval communication into their project workflows differently. They avoid sending preliminary approval unless they're prepared to accept production setup costs if formal approval fails. They recognize that any positive signal about approval status will trigger factory preparation, regardless of qualifying language. They document approval status internally without communicating it to the factory until all stakeholders have signed off. They treat approval as a binary gate—either the factory is authorized to proceed with full production setup, or they're asked to wait—rather than attempting to create intermediate states that preserve optionality without timeline impact.

The factories that successfully navigate preliminary approval scenarios are those that explicitly confirm cost liability before starting setup. When they receive preliminary approval, they respond with a message like "We understand you're giving preliminary approval. To meet your delivery timeline, we need to start printing plate manufacturing and material procurement now. If formal approval doesn't come through, the sunk cost will be RM 35,000 to RM 48,000. Please confirm whether you'd like us to proceed on this basis or wait for formal approval with a revised delivery date." This communication forces the buyer to make an explicit choice about risk allocation rather than assuming that preliminary approval preserves optionality without cost. Most buyers, when presented with this choice, authorize the factory to proceed and accept the cost risk. The explicit confirmation prevents the dispute that would otherwise occur if approval fails.

The preliminary approval trap also highlights how approval timing interacts with production economics. Buyers treat approval as a decision point that can be moved earlier or later in the timeline without affecting production costs. Factories understand that approval timing determines when setup costs are committed, and earlier approval enables parallel processing that reduces total lead time. When buyers send preliminary approval, they're attempting to signal approval direction without committing to approval outcome. But production setup doesn't work that way—setup either happens or it doesn't, and the timing of that decision determines whether the delivery date can be met. Preliminary approval creates the illusion that buyers can preserve both timeline and optionality, when in reality they must choose one.