A returned hollow base jack can look interchangeable with another adjustable component at first glance. That assumption creates avoidable confusion when several systems, project zones, or return lots arrive together. A short segregation note gives the yard team and buyer one shared record before anything is counted, quoted, reissued, or sent for further review.
Start with a return boundary, not a component count
Create one line for each physically distinct return lot. Record the sender, originating project or work area, arrival date, and any label or delivery reference that travelled with the items. If that information is absent, mark it as absent rather than assigning a likely origin.
This keeps a later count meaningful. A pile that combines separate returns may contain similar-looking parts with different intended systems, unknown history, or incomplete paperwork. The segregation note is not a substitute for project-approved inspection or installation requirements; it is a way to preserve the information needed for those decisions.
Use a four-field identification card for each lot
Before moving items into available stock, attach or maintain a card with four practical fields:
- Return identity: the lot reference, sender, and receiving date.
- Visible configuration: the apparent base-plate form, threaded member, adjustment nut, and any readable marking.
- Declared relationship: the system or package named in the return documents, if one is provided.
- Open decision: what still needs a drawing, order record, responsible project contact, or other approved evidence.
Describe what is present; do not turn a visual observation into an unverified material, load, size, or compatibility claim. That distinction is especially useful where the same return includes components associated with tube-and-coupler work. For sourcing discussions, keep the lot record alongside the enquiry sent to tube and clamp scaffolding suppliers so the requested parts are not detached from their known context.
Separate component families before proposing substitutions
A return note should make mismatches visible early. Place uncertain items in a clearly identified review area and keep them out of a release list until the responsible party has confirmed the intended relationship. Do not use a name match alone to group items from different systems or project packages.
A useful clarification prompt
Ask: “Which documented scaffold system or package is this item expected to support, and what record confirms that?” The question is more useful than “Will it fit?” because it asks for a traceable basis rather than a guess.
This also prevents unrelated product language from entering the wrong file. For example, an enquiry using the phrase best steel bed frame system should be held as a separate product-family question, not treated as evidence for a scaffold-return decision.
Turn unresolved items into a controlled follow-up
Close the note with named actions rather than a generic “check later.” State who will obtain the order reference or drawings, who will compare the reply against the lot card, and what event will allow the item to move from review to the next approved stage. If the information cannot be established, retain that limitation in the record instead of silently merging the item with available stock.
This approach is useful for distributors and project buyers handling returns from multiple locations. It preserves the distinction between a visible component, its claimed origin, and the evidence still required to make a responsible decision.
Build clearer return conversations
Bythai supplies scaffold systems and accessories for export-oriented project and distribution enquiries. When planning a new package or clarifying an existing one, bring the lot card, the applicable drawings, and the known project context into the conversation. That creates a more useful starting point than an unlabelled component list and helps keep product requests focused on the correct system.