{"id":8025,"date":"2026-11-12T23:34:50","date_gmt":"2026-11-12T23:34:50","guid":{"rendered":"https:\/\/koitorhardware.com\/?p=8025"},"modified":"2026-11-12T23:37:51","modified_gmt":"2026-11-12T23:37:51","slug":"shelf-capacity-vs-total-unit-capacity-buyers","status":"publish","type":"post","link":"https:\/\/koitorhardware.com\/es\/shelf-capacity-vs-total-unit-capacity-buyers\/","title":{"rendered":"Shelf Capacity vs Total Unit Capacity: What Hardware Buyers Should Specify"},"content":{"rendered":"

— The buyer should preserve the scope of shelf capacity vs total unit capacity in the drawing and approval record.<\/p>\n

When a metal storage rack shows a load limit, the buyer needs to know what the number applies to. Shelf capacity vs total unit capacity<\/strong> is a scope question: a stated limit may refer to one level, a complete assembled unit, a particular support configuration, or another clearly defined condition. A buyer should not add shelf figures, divide a total across levels, or transfer a number from a similar rack unless the responsible manufacturer has supplied evidence for that exact configuration.<\/p>\n

This guide helps importers and private-label teams preserve the meaning of load information from supplier documents through packaging and product listings. It does not calculate a rack rating, prescribe a test, or assign a capacity to any Koitor product. Koitor\u2019s exact product scope and any project-specific technical evidence must be confirmed directly for the design concerned.<\/p>\n

Why a shelf limit and a whole-unit limit answer different questions<\/h2>\n

A shelf-level limit concerns an identified level under stated conditions. A whole-unit limit concerns the complete rack configuration under its own stated conditions. Those statements are related, but they are not interchangeable. One does not automatically establish the other. A system can have more than one relevant constraint, and the buyer needs the manufacturer\u2019s definition of each one rather than an inferred value.<\/p>\n

Published maker materials illustrate why scope matters. Metro\u2019s guide presents level and unit limits for named shelving families with model-specific qualifications. TRINITY\u2019s product page distinguishes shelf or basket figures and total configuration information, including fixed-foot and wheel configurations for the named product. Those are examples of how specific product documents express limits. Their values and conditions apply only to the named products and must not be copied to another rack.<\/p>\n

The buyer\u2019s task is not to combine numbers mathematically. It is to preserve every applicable statement with its conditions and ask the responsible manufacturer what configuration was evaluated. If a document supplies only one scope, do not invent the missing one. Leave the field unresolved until the manufacturer provides the required information or until the buyer chooses to omit the unsupported claim.<\/p>\n

Define the exact rack configuration first<\/h2>\n

Before comparing load information, identify the physical configuration the document describes. Record the model or buyer SKU, drawing revision, number and type of levels, frame and support arrangement, installed accessories and whether the rack is configured as shown in the instruction or product image. A product-family name alone may not distinguish variants. The buyer\u2019s internal file should connect the evidence to the item that will actually be ordered and sold.<\/p>\n

Support mode can matter. A rack supported by fixed feet and one fitted with casters may be different configurations. If a manufacturer publishes separate information for those conditions, retain the distinction. Do not assume that a caster\u2019s own rating can be added to a frame rating or that a stationary figure remains valid while a rack is being moved. Ask the maker to state which conditions the relevant number covers.<\/p>\n

The number and type of levels matter too. Wire shelves, baskets, removable shelves and accessories may have different construction or support. If a level is replaced, omitted, repositioned, or fitted with another component, the documented whole-unit statement may no longer apply. A change in configuration should trigger a question to the evidence owner; it is not a basis for deriving a new limit independently.<\/p>\n

Record the loading conditions that accompany the maker\u2019s statement. These may describe how the load is placed, whether the limit applies per level or to the assembled unit, and any stated configuration or use qualifications. Do not add assumptions about uniform distribution, point loading, movement, floor condition or duration. Use the manufacturer\u2019s own wording and request clarification where it is incomplete.<\/p>\n

Keep the load-limit record explicit<\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n
Specification field<\/th>\nBuyer should record<\/th>\nLo que no hay que deducir<\/th>\n<\/tr>\n<\/thead>\n
Product identity<\/td>\nSKU\/model and controlled drawing revision<\/td>\nThat every item in a family is identical<\/td>\n<\/tr>\n
Level identity<\/td>\nShelf, basket or other named component<\/td>\nThat unlike levels share one value<\/td>\n<\/tr>\n
Level limit<\/td>\nManufacturer-stated value and conditions, if supplied<\/td>\nA value derived by dividing the complete-unit number<\/td>\n<\/tr>\n
Whole-unit limit<\/td>\nManufacturer-stated value and conditions, if supplied<\/td>\nA value derived by adding the levels<\/td>\n<\/tr>\n
Support mode<\/td>\nFixed feet, casters or other stated configuration<\/td>\nThat one mode inherits another mode\u2019s limit<\/td>\n<\/tr>\n
Configuraci\u00f3n<\/td>\nNumber, type and location of levels\/accessories<\/td>\nThat a modified rack retains the original statement<\/td>\n<\/tr>\n
Evidence source<\/td>\nControlled document, revision and responsible issuer<\/td>\nThat a retailer summary replaces the source record<\/td>\n<\/tr>\n
Approved wording<\/td>\nExact claim and required qualifications<\/td>\nThat a short headline can omit material conditions<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The table is a recordkeeping framework, not a test protocol. Where the manufacturer provides both per-level and whole-unit statements, preserve both. Where a required statement is missing, mark it \u201cnot supplied\u201d or \u201cpending clarification.\u201d Do not use blanks as an invitation to calculate. A buyer may decide not to publish a particular claim if its meaning cannot be confirmed.<\/p>\n

An example can be explained without inserting a made-up number: a proposed loading plan must be checked against each applicable manufacturer-stated constraint. A plan that appears to respect one limit does not show that another limit is satisfied. This observation does not provide permission to load a particular product, and it is not an engineering calculation. The responsible product manufacturer must define the applicable constraints and their evidence.<\/p>\n

Ask what the manufacturer\u2019s document actually proves<\/h2>\n

When a supplier provides a technical sheet or test summary, check the title, product identity, revision, configuration, scope and author. Is the statement for a component, one shelf, a complete assembled unit, or a family of models? Does the document identify the fixed-foot or caster setup? Does it specify loading conditions and applicable limitations? Is the referenced test or evaluation described, and is the result connected to the product revision being quoted?<\/p>\n

A document\u2019s presence is not the same as a buyer understanding its scope. A marketing page may summarize a maker\u2019s claim; a technical document may provide more detail. The buyer should retain the controlling source and ask the manufacturer to resolve any mismatch. Do not describe a manufacturer statement as independently verified unless an appropriate independent review has actually occurred.<\/p>\n

Also separate a load limit from other product qualities. A load statement by itself does not establish stability, tip resistance, fatigue life, corrosion resistance, installation suitability, safe use in every environment, or compliance with a standard. Those properties require separate definitions and evidence. Keep each product claim tied to the specific basis that supports it and avoid implying that one number proves a broader performance outcome.<\/p>\n

OSHA\u2019s materials for warehousing include the general instruction that storage structures should not be loaded beyond their rated capacity and that load limits should be posted where applicable. That workplace guidance is context, not a rack design calculation, not an assignment of any particular rating, and not a substitute for the manufacturer\u2019s product-specific information. Buyers must assess applicable workplace and jurisdiction requirements with qualified personnel.<\/p>\n

Check feet, casters and movement as separate conditions<\/h2>\n

A stationary rack and a rack on wheels may present different use and support conditions. Review the exact product documentation for each offered setup. If the supplier\u2019s table gives separate figures or conditions, maintain them separately in the buyer\u2019s specification and product listing. Do not combine them or assume the more favorable number applies in every situation.<\/p>\n

Ask whether the manufacturer\u2019s information covers the rack while stationary, while being moved, or both, and how a caster option changes the documented configuration. Do not derive a whole-rack statement from individual caster labels. A component rating and an assembled-product rating answer different questions and may have different assumptions. Where the supplier has not provided an answer, treat the condition as unresolved.<\/p>\n

The same care applies to floor surface, leveling and positioning. A rack that is not assembled or installed as documented may differ from the evaluated configuration. This article does not provide a setup procedure or a surface-suitability claim. Follow the product manufacturer\u2019s instructions and seek clarification where the intended use differs from them.<\/p>\n

If wheels or adjustable supports are optional, identify the exact option code and installation state in the product record. Packaging, listing text and instructions should not make it appear that two configurations share one approved rating when the evidence distinguishes them. This is especially important when the option changes after initial product approval or when marketplace content is copied between variants.<\/p>\n

Treat removable or changed shelves as a configuration question<\/h2>\n

Removable shelf designs can let a buyer change storage layout, but a physical ability to remove a level does not establish that every altered arrangement retains the same documented limit. Ask the manufacturer which configuration the evidence covers and whether a modified setup has a separate statement. Keep the approved assembly and any permitted alternatives in the product record.<\/p>\n

If the rack has baskets, shelves or attachments with different roles, identify each by its correct name. A \u201clevel\u201d may not be one uniform part across the complete unit. A tray, basket and solid shelf can differ in construction, support geometry and intended use. Do not copy one part\u2019s documented limit to another because they occupy a similar position.<\/p>\n

A change to a level count can also change how a customer perceives a total capacity statement. That perception should not be addressed through unsupported arithmetic. If the buyer wants to market a configuration with a removed or repositioned component, request manufacturer confirmation for the exact item, revision and assembly. If no confirmation is available, do not describe the changed arrangement as rated to the original limit.<\/p>\n

For buyers evaluating removable-level architecture, a separate design review should address configuration changes. This article focuses on preserving the scope of load statements and should not duplicate a design or structural analysis.<\/p>\n

Separate capacity, stability and intended application<\/h3>\n

Buyers sometimes compress several concerns into the word \u201ccapacity.\u201d Clarify whether the question is a documented load limit, the number of levels, the available storage volume, a product\u2019s advertised basket count, or stability in a specified setup. These measures are not interchangeable. A rack may have a stated load value while other product questions still require separate review.<\/p>\n

If the intended application includes concentrated, shifting, unusually shaped or potentially hazardous items, provide that context to the supplier and request a project-specific review. Do not assume that a general product page covers an unusual load pattern or operating environment. This guide does not recommend placing people, climbing, or other uses outside the manufacturer\u2019s intended application.<\/p>\n

Likewise, an overall rack limit does not by itself tell a buyer how to distribute items across levels. Any placement instructions must come from the product\u2019s approved documentation. Do not create a loading diagram by dividing a total or applying a ratio unless the manufacturer has supplied and approved that method for the exact rack.<\/p>\n

The buyer\u2019s marketing team should keep the product description aligned with the manufacturer\u2019s technical wording. Avoid changing \u201cper shelf under specified conditions\u201d into a bare headline that readers could interpret as the total for the entire product. Conversely, do not describe a total-unit statement as a limit for each individual level. Use clear labels and repeat necessary conditions near the claim.<\/p>\n

Carry the qualification through packaging and digital listings<\/h3>\n

The load statement often travels from a supplier document into a product data sheet, carton, instruction leaflet, retailer portal and ecommerce listing. Each handoff can remove the context that made the original statement accurate. Assign an owner to approve the exact wording and ensure that the scope, configuration and conditions remain visible wherever the claim appears.<\/p>\n

Use a controlled source document and revision, not a copied fragment from an old listing. If the supplier changes the frame, level, accessory, support mode or assembly, ask whether the prior load information remains applicable before reusing it. Product imagery should depict the configuration described in the text. If a listing shows casters but the stated information applies to fixed feet, the mismatch needs resolution before publication.<\/p>\n

For multi-variant listings, connect each value to the correct model. Do not display one number for an entire family if the source differentiates configurations. Retailer systems may have limited fields; the buyer still remains responsible for communicating a clear and supportable claim in the available content. If a platform cannot preserve the necessary qualification, escalate it through the product and compliance review instead of silently dropping it.<\/p>\n

Carton or instruction copy should also avoid implying a broader test result. A load figure does not prove that the item will tolerate every transit, assembly or use condition. Keep packaging, installation, stability and performance claims separate unless the evidence supports each one. This discipline protects clarity for the buyer, supplier, retailer and end user.<\/p>\n

Questions to send with an RFQ or product review<\/h3>\n

Ask the manufacturer to identify which limits are established for the exact offered configuration and what source controls them. Request the level-level and full-unit scopes separately where applicable. Ask whether the configuration uses fixed feet, casters or other support, and whether any conditions differ between stationary and movement states. Confirm the number and type of levels, accessories, assembly revision and any stated loading conditions.<\/p>\n

If the supplier provides an existing document, ask which SKU, drawing or model it covers and whether the quoted product matches it. Ask whether the document is the current revision and whether a planned change affects its applicability. If the evidence is a test report, request the stated scope and test identity, while avoiding the assumption that a test name alone proves suitability for every use.<\/p>\n

The buyer can make the request practical by attaching the intended product drawing, proposed configuration, support option, planned listing wording and any known use conditions. Identify who will approve technical meaning and who will approve consumer-facing copy. The manufacturer can then respond within its actual evidence and capabilities; the buyer should not ask it to create a rating from unspecified conditions.<\/p>\n

Frequent errors to prevent<\/h3>\n

Adding all shelf values to create a total.<\/strong> This assumes that the per-level figures can be combined without another system constraint. Use only a whole-unit statement supplied for the exact configuration.<\/p>\n

Dividing a unit value to create a per-level claim.<\/strong> This assumes equal load limits and ignores the level structure and manufacturer\u2019s evidence. Ask for the level-specific information if it is required.<\/p>\n

Copying a rating from a similar model.<\/strong> Similar appearance or a shared family name does not establish identical dimensions, materials, supports or evidence. Match the document to the offered item and revision.<\/p>\n

Treating feet and casters as equivalent.<\/strong> Keep support-mode-specific conditions visible and ask what the manufacturer\u2019s figure covers.<\/p>\n

Assuming removable levels preserve the original statement.<\/strong> The altered arrangement may not match the evaluated configuration. Obtain confirmation before using the same claim.<\/p>\n

Using load capacity as proof of safety or durability.<\/strong> A single statement does not establish all structural, installation, stability or lifecycle properties. Keep claims distinct and evidence-based.<\/p>\n

Dropping qualifications in the listing headline.<\/strong> Retain the scope and conditions close to the number so readers can tell what it describes.<\/p>\n

A buyer approval checklist<\/h3>\n

Before approving a load-related statement, verify:<\/p>\n

    \n
  1. Does the source identify the offered model, SKU or controlled revision?<\/li>\n
  2. Is the statement for a level, the complete unit or another named scope?<\/li>\n
  3. Are different shelf or basket types identified separately where necessary?<\/li>\n
  4. Is the support mode stated, including fixed feet or casters where relevant?<\/li>\n
  5. Are stationary and movement conditions distinguished if the source does so?<\/li>\n
  6. Does the documented configuration match the assembled product being sold?<\/li>\n
  7. Are changes to removable or repositioned parts covered by the source?<\/li>\n
  8. Are loading conditions and qualifications retained in the approved wording?<\/li>\n
  9. Is a named evidence owner responsible for technical questions?<\/li>\n
  10. Does packaging and digital content use the same approved claim?<\/li>\n
  11. Have stability, installation and other separate claims been reviewed independently?<\/li>\n
  12. Are any missing data clearly labeled as unresolved rather than inferred?<\/li>\n<\/ol>\n

    This list is deliberately a document-control aid, not a structural rating method. If the product team cannot answer a question from the available source, it should assign the question to the responsible manufacturer or qualified reviewer. A missing value should remain missing until the correct evidence owner supplies an answer.<\/p>\n

    Preguntas frecuentes<\/h3>\n

    Is total unit capacity just the sum of all shelf capacities?<\/h3>\n

    Do not assume so. A shelf figure and a whole-unit figure have different scopes. Use the manufacturer\u2019s statement for the exact assembled configuration and do not calculate one from the other unless the manufacturer explicitly supplies an approved method.<\/p>\n

    Does a shelf limit apply when the rack is on wheels?<\/h3>\n

    Only if the responsible manufacturer\u2019s documentation says it applies to that configuration and condition. Check whether the document distinguishes fixed feet, casters, stationary use or movement. A wheel component statement does not substitute for an assembled-rack statement.<\/p>\n

    Can I keep the same rating after removing one shelf?<\/h3>\n

    Do not assume that a modified arrangement is covered by the original document. Ask the manufacturer whether the exact changed configuration is addressed. A shelf\u2019s removability does not itself establish an alternate rating.<\/p>\n

    Does a capacity claim prove the rack is stable?<\/h3>\n

    No. Capacity and stability are distinct product questions. A load statement alone does not establish tip resistance, installation suitability, durability or safe use in every condition.<\/p>\n

    What if the supplier gives only one number?<\/h3>\n

    Record exactly what the source identifies and request clarification if a second scope is needed. Do not divide, multiply or transfer the value to fill a gap. The buyer can omit an unsupported claim until the evidence owner resolves it.<\/p>\n

    Can I reuse a number from a similar product in the same range?<\/h3>\n

    Not without confirmation that the source applies to the offered model and configuration. Similar appearance or branding does not prove that the underlying product and evidence are the same.<\/p>\n

    Sourcing takeaway<\/h3>\n

    Treat every load statement as a scoped claim. Identify the exact rack, level type, assembly, support mode and manufacturer source; preserve shelf and whole-unit limits separately; and keep the accompanying conditions visible in packaging and listings. Never derive a missing value from another number or copy it from a similar product.<\/p>\n

    For a metal-rack OEM discussion, share the controlled drawing, intended configuration, support option and proposed wording with the supplier and ask which evidence applies. Koitor\u2019s P\u00e1gina de fabricaci\u00f3n de estanter\u00edas met\u00e1licas a medida<\/a> is the relevant project contact route; it does not establish a certified capacity for any product. Caster selection and removable-shelf architecture are separate decisions and do not replace the maker\u2019s current load documentation.<\/p>\n

    \"Rack<\/figure>\n
    \"Buyer<\/figure>\n

    Sources and scope notes<\/h3>\n