Warehouse Operations Guide

Warehouse Labeling for 3PLs: Location Labels, Product Barcodes, and Scan Verification

Warehouse labeling works when each label identifies a defined object and the warehouse management system (WMS) checks that object against the active task. Start with the owner, product variant, packaging unit, location and expected action. Then choose what to print and test which record changes after a scan.

Consider a hypothetical packing station that can read the barcode on a new client’s carton. The application finds a similarly named variant from another account and lets the operator continue. The scanner performed its job. The failure occurred in the lookup or task check. Before deploying labels, verify what the device decodes, which record the string resolves to, whether the task permits that record and what quantity or status the confirmation posts.

The same sequence applies to a bin, a retail item, a full case, a tote and an outbound parcel. Decide what object the operator is handling at each step and give that step an expected record. If the application cannot distinguish two eligible records, resolve the ambiguity before posting the work. You can pilot that decision in one account and area before changing a warehouse full of labels.

Warehouse worker holding a scanner checks a carton beside rack label holders in a small facility.
Illustration of a 3PL worker using a scanner to check a carton beside a rack label.

What does each warehouse label identify?

Separate the identifier, its representation and the record it refers to. A location name is a string. A barcode can encode a string according to a symbology, and a printed label carries that symbol with readable text. The location record defines where the bin is and which operations are permitted. Reprinting a label does not edit the record. If a scanner adds a prefix or suffix, establish which characters the application actually receives before troubleshooting a mismatch.

LabelIdentification and use
LocationObject · Physical bin or rack position
Print · Readable address and direction when needed
Record · Facility location ID and attributes
Scope · Define for the site and WMS lookup
Scan · Putaway, pick, move or count
Common mix-up · Scanning an item code to confirm a bin
ProductObject · Item variant or selling unit
Print · Short description, variant and SKU when useful
Record · Client item and external code map
Scope · Depends on account and item lookup; a trade item can share its GTIN across owners
Scan · Receipt, pick or packing check
Common mix-up · Inferring ownership or serial identity from GTIN
Case or packObject · Defined packaging configuration
Print · Unit and verified contents per pack
Record · Packaging item or unit conversion record
Scope · Depends on packaging and lookup rules
Scan · Full-case receipt, pick or count
Common mix-up · Treating a short or mixed carton as a standard case
ContainerObject · Specific tote, pallet or handling unit
Print · Visible container ID
Record · Handling unit and current assignment or contents
Scope · Define uniqueness and reuse in the WMS or partner scope
Scan · Grouping, movement and handoff
Common mix-up · Using a prior assignment after reuse
Shipping labelObject · Outbound parcel in the shipping workflow
Print · Required transport and routing information
Record · Active label, package and shipment records
Scope · Use the carrier and application’s tracking and label rules
Scan · Pack confirmation and carrier handoff
Common mix-up · Using an old label for a different parcel

A stock keeping unit (SKU) is an internal product identifier. Ask whether its uniqueness is scoped to a merchant, an account or the whole installation. A Global Trade Item Number (GTIN) identifies a trade item. A UPC-A symbol can carry a GTIN-12. Multiple units of the same trade item can share that GTIN, and stock owned by different clients can carry the same manufacturer label. If your task needs serial or lot information, capture the required attributes explicitly through supported fields. GS1 US on GTIN, UPC and SKU

The trade item may be a selling unit or a defined packaging level. Record the relationship between the case configuration and the units it contains. The quantity per case belongs to that mapping. It cannot be inferred from the length of a barcode or the fact that a label sits on a carton. A mixed case may contain more than one item identity. GS1 US packaging levels

A license plate number (LPN) is an internal identifier used by some WMS workflows to refer to a handling unit or its contents. Confirm how your system issues it and when the association is closed or reused. A GS1 Serial Shipping Container Code (SSCC) identifies a logistic unit for sharing across supply chain parties. A tracking number belongs to the transport record. Those identifiers can be linked to the same physical box for different purposes. Choose the ones the work and trading partners require. Internal bins and totes can use identifiers supported by the warehouse system. GS1 US on SSCC

Five label types link to different records: location, product, case, internal container and outbound shipping label.
Label objects and their records. Symbols are illustrations only and cannot be used for business scanning.

If a parcel has a replacement transport label, confirm which label record is active and which physical package carries it. A reprint may reproduce the same label, while a replacement can have a different association. Keep the outbound check tied to the packed parcel and the intended shipment so an old sticker does not drive handoff.

When a tote carries picked goods from several orders, its identifier should resolve to the assignment and contents that the current workflow expects. At packing, reconcile the contents to the order and the actual parcel before linking the shipping label. Use the batch picking guide for the sorting workflow and the order, shipment, package and label guide for the outbound record relationships.

Which data and naming rules come before printing?

Start with a list of records the warehouse can check. Keep the client, facility, internal item ID and variant, the client’s SKU and external identifier mapping, unit of measure and conversion, location, container assignment and active status. Where applicable, track the lot or serial requirement. For every lookup, write down which fields narrow it and what happens if no record or several records match. A mapping needs a responsible owner and an effective date so a shift lead can explain why it exists.

A useful lookup can return several fields to the operator before confirmation, including the client, short item description, variant and expected unit. Show where the decision is made if a code is reused. For example, the task can choose an owner first, then the item lookup can be restricted to that owner’s active records. Ask the system owner to demonstrate the rule using a conflict, not just a known good label.

Set an exception path for unknown or ambiguous values. Keep the current task and its quantity open, capture the received string and location, and route the record to the person who owns that mapping. If manual lookup is permitted, require the operator to confirm the expected variant, owner and unit before posting through that path.

For existing product barcodes, verify the physical label and the exact variant and package it represents. Check the lookup in every intended task, including receipt and packing. Reuse the manufacturer symbol when the application can resolve it unambiguously within the supported context and quantity rules. For a warehouse-generated code, verify the accepted field, format, scope, parser and task behavior first. Agree how the operator will choose between the two symbols if both remain on the package.

A defined packaging map could link a product record to an each unit and a specific case record with a factor. Give the case mapping an approval source, such as verified product data and a physical check. Use an effective date for a new pack and keep old stock distinguishable during transition. If a supplier reports a trade-item case quantity change, confirm the assigned case identifier with the brand or supplier under the applicable GS1 rule. A short carton in a receipt is a count discrepancy to record for that carton. GS1 GTIN Management Standard, pack and case quantity

Test the data exchange between the sender and receiver as well as the screen. The same carton can be described by a client’s SKU, a warehouse item ID and a supplier case identifier. Save the original identifiers with the cross-reference, and record which unit each system sends. If a mapping changes, review any queued imports or open orders that may still carry the prior version.

For a location, write a human-readable address that someone can find on the floor. In this example, A-01-03-02 means zone A, aisle 01, rack 03 and level 02. If the rack has several bins per level, decide whether a further segment is needed. Choose segment widths and separators for the actual facility and supported characters. Walk sample names from a station to a shelf. Check for lookalikes such as O and zero, sorting behavior and available addresses for expansion. Test routing separately using the warehouse’s task rules.

ShipHero’s naming guide discusses consistent segments and physical rack placement in its context. Its location management documentation also describes location properties and individual or bulk maintenance. Use the supported edit path and test the effect on active work in your own account. A naming pattern alone gives no assurance about a route or about how historical references will behave. ShipHero naming guidance · ShipHero location management

Print the information that helps the operator select or verify the object at the station. A bin needs a readable address. A product label may need a short description and variant. A case should show its unit and confirmed pack quantity if the operator will use them. A tote needs an identifier clear enough to distinguish it from its neighbor. Keep mapping provenance, record keys, change history and other administrative fields in the register where they can be searched.

Select the symbol for the data and the real equipment. Check whether the intended devices support the symbology at working distance and under site lighting, whether the application parses the payload, and what a trading partner requires. A 2D symbol may fit a supported workflow with several data fields. A supported linear symbol may be adequate for a short lookup key. Validate any compound payload before using it. Adding a client prefix can turn the entire string into a different lookup key.

How should the label work on the floor?

Make the printed text refer to the same object as the encoded content. Verify them against the print source and master record before printing a batch. Test contrast, quiet zones, clarity and print scaling using the applicable symbology and equipment documentation. If a partner specifies barcode quality verification, use the relevant verification method and equipment. A handheld scanner check can establish readability under the sampled conditions. GS1 barcode quality guidance

Place the label where the user can aim at it from the working position, with enough separation from neighboring labels. Check actual angles and distance on the shelf, cartons under wrap, gloss, curved surfaces and labels near seams or edges. Try the device the next shift will use. A bench scan of a flat proof is a useful first check. The installed label still needs a test in its intended task and position.

Choose stock and adhesive for the surface and expected temperature, moisture and abrasion. A reusable container can use a removable job association alongside a durable container ID if the workflow supports both. A permanent bin address needs material that holds up over its expected life. Walk the area for curled edges, fading, damage and old labels. Remove or fully cover obsolete symbols as appropriate while preserving required labels and evidence. Document each replacement and confirm where the code now resolves. ID Label warehouse labeling overview

When a bin label sits above the position it names, make the direction explicit in the text or layout. Walk the row from both directions with someone unfamiliar with it. At a pack station, present the case or each label in a consistent place. Test whether a worker can select it when neighboring labels are visible.

Suppose a larger print makes a product code easy to read, but its item mapping still points to the wrong size. The larger symbol makes that incorrect lookup easier to repeat. Hold the affected work, inspect the payload and update the approved mapping before changing the print batch. For media and device selection, use the shipping label printer guide and test the materials needed for this location or item.

What should happen in four common exceptions?

The following cases are hypothetical. Use the examples to write expected outcomes for a controlled test before relying on the labels for live transactions.

1. The same product barcode appears under two owners

Client A and Client B carry the same manufacturer’s item and packaging level. The trade item and manufacturer barcode can match while the inventory has different owners. The failure occurs if the application looks up the barcode across all eligible accounts and selects a record before it establishes which stock the receiving or picking task can use.

Start with the client on the authorized receipt or pick task. Compare the item lookup to the client’s master record and confirm the owner on the chosen location, handling unit or inventory record using the controls your WMS supports. If the application supports client-scoped lookup, validate that configuration. If the relevant field must be unique across the account, evaluate supported account separation or an internal identifier mapped to the client item. Preserve the manufacturer GTIN as product data. ShipStation documents a SKU and UPC uniqueness requirement for its products and selectable scan verification fields in its workflow. Check the rule in the actual product and account you use. ShipStation UPC and SKU settings

Run a positive test for A and a negative test using B’s known stock record or container in an A task. Capture the task owner, selected stock and resulting transaction. With identical unmarked units, a shared symbol cannot reveal which pile a unit came from. If the application lacks an enforceable check, use physically separated owner inventory, task-specific access and a second-person verification before posting. Record who checked it and hold the rollout where the remaining risk is unacceptable. An operator check remains dependent on following the process.

Document the failure path as carefully as the success path. If a test selects B’s record, stop that task and keep the carton with its verified owner. Save the lookup inputs and expected record before editing data. If inventory already posted to B, use the authorized correction process and reconcile both owner balances. Rerun the wrong-owner test before clearing the area.

The same manufacturer code on two items links to different owner stock through client-specific tasks and inventory records.
Teaching example. The task and stock record establish the owner. The manufacturer code stays the same.

2. A case scan needs a verified unit and quantity

The receiver finds 12 complete cases of the same approved configuration, each containing 24 units. The expected base quantity is 12 cases × 24 eaches per case = 288 eaches. A scan might identify one case record, confirm one of the expected cases, or increment an each quantity, depending on the configured task. The count of successful reads alone does not tell you which value was posted.

Choose one conversion point. If the receipt is expressed as 12 cases and the WMS expands it to base units, send the case quantity and check that the result is 288. If an import has already normalized the receipt to 288 eaches, use the each unit in the posting path. Verify the source quantity, input unit, mapping factor and stored balance. A second multiplication after conversion would record too much stock.

Now suppose one carton contains only 20 pieces, with the other 11 confirmed at 24. The physical total is 11 × 24 + 20 = 284 eaches. Pause the affected receipt or line before accepting the standard case quantity. Record the container, count, unit and discrepancy. Use the supported partial-case or each-level entry and obtain approval when required. Check that the final receipt adds 284 under the correct owner and that the exception can be traced. Use the receiving SOP for the handoff and discrepancy record. Mixed or open cases and a new case configuration need their own verified quantity basis.

Agree which quantity the operator should read back at confirmation. The screen may show case quantity, each quantity or both. The supervisor compares that display with the receipt history and the item’s base-unit balance, accounting for other movements in the same interval. For an unresolved count, isolate the affected carton and preserve the rest of the verified receipt for supported partial processing.

Twelve verified full cases at 24 eaches give 288 eaches. With one 20-piece carton and 11 full cases the verified count is 284.
Teaching assumptions. Apply the verified case conversion once and resolve the short carton before posting.

3. A new location name must survive open work

A rack position stays in the same place. The warehouse wants to display A-01-01 where it previously used A-1-1. The risk is that labels, active tasks and reporting references change at different times. One clerk could use the new sticker while another task still points to the old reference.

List the location’s existing identifier, stock and attributes, and inspect open picks, counts and moves. Determine how the WMS edits a name, whether tasks resolve through a stable record ID or a stored string, and whether an alias is supported. Agree how existing tasks will finish, pause or be reissued. Keep a change record with the old and new names, facility, physical position, effective time and reviewer. If the platform cannot rename safely with work open, stop or close the affected work first and follow its supported migration.

Replace the physical label at the agreed time and remove the old active symbol. A supported alias, if needed for transition, should map to the same record and have an expiry and explicit expected behavior. Avoid creating a second live location as a shortcut. Walk to the bin, scan it in the actual task, and confirm the same intended position, owner stock and quantities. Check the retired code according to the alias policy and reconcile the open tasks. The rename itself makes no inventory move. Use the slotting guide if the physical placement is also changing.

Include terminals with cached or downloaded tasks in the cutover check where applicable. An old task may still show a prior display name after the central record changes. Confirm whether it can finish correctly against the same position. If workers cannot confidently locate and verify it, pause those tasks and refresh or reissue them through the supported process.

4. A spreadsheet drops the leading zeros

An internal product identifier is stored as the text 001234. A spreadsheet imports it as a number and exports 1234. These are fictional internal strings. A scanner can decode 001234 exactly and still fail to find the intended item. If the shortened value happens to exist elsewhere, the lookup may even produce a wrong match.

Export a reference copy of the master data, then import code columns explicitly as text. Review automatic type conversion steps and compare the raw export or saved CSV with the original before loading it. A display format can show zeros while a downstream file still has a different value. Do a small controlled import with known items, check what the product record stores and see which other fields the import changes. Microsoft documents text import for preserving leading zeros in Excel. ShipStation’s documented product CSV workflow can replace existing details, including clearing fields from blank cells. Microsoft Excel text import · ShipStation product CSV guidance

First verify the decoded string, then run it through a real task in the intended account. Try the correct code, another variant’s code, an unknown string and a record or container from the wrong owner. Check both the operator message and the resulting state. Test repeat scans against the task’s quantity and serialization rules. A second scan may confirm another identical nonserialized unit when two are required. An extra scan beyond the task quantity should be rejected under the proposed test rule, with no extra posting.

Save the raw fixture values as text, including the shortened value for the failure test. Do not add leading zeros to every code as a blanket fix. Some shorter values may be legitimate in their own namespace. Distinguish a worker scanning another unit from the application resubmitting the same confirmation after a timeout. In the latter case, check transaction history before retrying so the same movement is not posted twice.

How do you replace labels without interrupting the wrong work?

Inventory the labels and assign owners

Start with a floor walk and a data export. Record the visible label, actual decoded payload where safe to sample, record and status, and the task that uses it. Include alternates and obsolete marks near the active one. Give location naming to a warehouse lead, item and pack mappings to a master data owner, and print approval and installation to named operators. Assign a person to accept the business result in the WMS.

Clear conflicts and pilot one account and area

Review duplicate values in the scope the application actually searches. Separate valid reuse across clients from ambiguous mappings within a task. Hold inactive mappings and confirm the unit definitions before printing. Start with one client and one area, including adjacent labels and the device types used there. Save the prior mappings and labels so you can restore the configuration and reconcile affected tasks if the pilot has to stop.

Test proofs, installation and the real transaction

Compare the proof’s text and decoded value with the approved record. Install in the intended location and scan from normal working positions, then use a controlled receipt, pick, pack or movement task. Run correct and deliberately wrong inputs. Inspect inventory, container or package records after confirmation. Confirm rejected inputs leave the affected records unchanged. If an error is only a warning, determine whether staff can override it and who can approve an override.

Coordinate open work, remove old labels and expand

Record which tasks will be completed under the prior setup and which must be reissued. Replace the old labels at a defined handoff and review the new record and physical address together. Record exception, batch, operator, time and retest. Pause expansion for owner mismatches, unknown case factors or old symbols that cannot be removed or reliably controlled. Expand after the approved exceptions have been resolved and the lead has reviewed both passing and blocked work.

If a rollout is paused, mark the affected task and label batch before changing either. Reconcile transactions that were accepted during the pilot against the last known good record and the stock on the floor. Use approved corrections where needed. A rollback should restore a consistent mapping and label for the same object and preserve the trace of work that actually occurred.

Budget labor by task

For a hypothetical project, data cleanup takes 120 minutes. Installing 320 location labels at 60 seconds each takes 320 minutes. The initial scan check at 15 seconds per label takes 80 minutes. Handling 20 exceptions at three minutes each takes 60 minutes. Total planned effort is 580 person-minutes, or nine hours and 40 minutes.

In this example, the installation time covers placement at the face of the location, and exception time covers the listed review and correction. Add separately any walking, device waits, elevated work, additional rework and system configuration. Elapsed project time depends on staffing, access and task sequencing. Measure one small batch and replace the assumptions before scheduling a larger cutover.

What does a useful scan acceptance test prove?

Observe four things separately. First, a real device reads the installed symbol in the working position. Second, its string resolves to the expected active record. Third, the record is legal for the current owner, location, unit and task. Fourth, the resulting business event has the intended quantity and status. For rejected inputs, confirm both the operator response and the absence of an incorrect movement. A decoding app alone covers the first part of a broader check.

Specify the setup, device, application version or configuration, expected result and reviewer. Save the task reference and the before and after record when appropriate. Test normal distance and angle and the neighboring label. Then change one condition at a time so an error can be attributed to the mapping, device, placement or task. Recheck after a print template change, product data import, location change or a change to scanner settings.

MeasureCalculation and sample
First-read successCorrect target reads on the first attempt ÷ sampled attempts at eligible installed labels. Define normal distance, angle, devices and tasks.
Blocked-error test passDesignated invalid scenarios with the expected rejection and no wrong posting ÷ all designated invalid tests executed. Keep normal tests separate.
Exceptions per thousand operationsLabel or mapping incidents × 1,000 ÷ related operations logged in the same task scope and time window. Define repeat attempts and incident counting.

Use comparable samples before and after the rollout. State the client, item mix, devices, shifts and tasks sampled. Keep first reads, blocked error tests and confirmed operations as different denominators. Investigate high exception counts by cause and write down what action was taken. A first-read measure tells you about readability. Review order and inventory accuracy using the corresponding business records. The cycle counting guide covers reconciling physical and recorded quantities.

For example, if a device consistently reads a neighboring shelf code first, record that as a wrong-object read under your stated first-read rule. Track the subsequent rejection separately if the task correctly stops it. The same attempt can reveal a placement issue and demonstrate that a task check is working. Review both findings before choosing whether to move the label or change the interface.

A pilot review should list the sample size alongside each measure and keep the excluded cases visible. For example, a damaged label removed before the first-read sample still belongs in the damage log. Use the log to decide whether to change the material, print setup or replacement process. Recheck the affected tasks after the change.

What should the team record for rollout and maintenance?

Use the register to tie each printed label to its approved record and scope. Keep the payload as text and enter the symbology supported by the application after testing. The download includes fictional rows and a blank entry. Its format choices are candidates to validate. Print only the fields needed on the floor. Preserve the internal record, approval, status and print history in the register. Use a separate record for a changed case factor or retired location name so an old batch can be identified.

Register exampleSample values and usage
LocationA-01-03-02 resolves to LOC-10302 in WH-DEMO. Print the address and keep record ID, scope and batch in the register.
Product001234 is text for client A’s blue M each. Print the readable variant and retain the approved lookup, format and dates in the register.
CaseC24-A-BLU-M refers to the verified 24-each configuration. Show case and count if used on the floor. Keep conversion approval in the register.
ContainerDEMO-T07 refers to an internal tote and the active assignment. Print the tote ID and keep the changing assignment in the system.
CopyDownload the register with four fictional rows and a blank entry

Use the acceptance worksheet to describe what the task should accept or stop. In the sample, no actual result or retest is filled in. Before running the cases, substitute authorized test records and confirm the expected behavior with the process owner. A test can be performed in an isolated account or controlled task. Reserve live inventory changes for authorized work. Store evidence of the posted event or unchanged record with the test result.

TestSetup and expected result
T01Task · Pick one unit
Expected object · Blue M each
Input · 001234
Context · Client A / WH-DEMO
Expected · Allow and confirm one each.
T02Task · Pick one unit
Expected object · Blue M each
Input · 001235 mapped to blue L
Context · Client A / WH-DEMO
Expected · Block wrong variant. Quantity unchanged.
T03Task · Pick one unit
Expected object · Blue M each
Input · Unmapped 001999
Context · Client A / WH-DEMO
Expected · Block unknown input. Quantity unchanged.
T04Task · Pick for Client A
Expected object · A-owned blue M stock
Input · Select B-owned tote with same trade item
Context · Client A task / WH-DEMO
Expected · Block B stock selection. Both owners’ balances unchanged.
T05Task · Pick two units
Expected object · Two nonserialized blue M eaches
Input · 001234 twice on two physical units
Context · Client A / WH-DEMO
Expected · Allow both and confirm two eaches.
T06Task · Pick two units, already confirmed
Expected object · No remaining quantity
Input · Scan 001234 a third time
Context · Client A / WH-DEMO
Expected · Block extra scan and post no additional units.
T07Task · Import or pick
Expected object · Blue M internal code 001234
Input · Truncated text 1234
Context · Client A / WH-DEMO
Expected · Flag changed text in import. If unassigned, block pick with no posting.
T08Task · Receive verified cases
Expected object · 12 full cases at 24 eaches per case
Input · 12 cases on approved C24-A-BLU-M mapping
Context · Client A / WH-DEMO
Expected · Allow one conversion. Post 288 eaches.
T09Task · Resolve short case
Expected object · 11 full cases and 20 pieces
Input · One carton physically has 20
Context · Client A / WH-DEMO
Expected · Hold the standard case posting. After approved correction, post 284 eaches.
T10Task · Check renamed location
Expected object · Same position under A-01-01
Input · Retired A-1-1 after alias expiry or with no alias
Context · WH-DEMO / authorized task
Expected · Block retired code. Confirm new code resolves to same intended position.
CopyDownload the acceptance worksheet. Actual result and retest columns are blank.

Before the next shift, identify who owns replacements, mapping corrections and exception review. If a label is damaged or ambiguous, hold the affected object and confirm its identity through the approved record. Print a replacement from that record, retire the old symbol and rerun the relevant checks. Periodically sample installed labels and review mappings after client onboarding, packaging changes and software updates.

Once the owner, items, quantities and packed parcel are confirmed, move the verified data to rate comparison, shipping label creation and handoff. EasyShippingX’s public shipping workflow offers rate comparison, label creation through the Portal, Excel upload or API, and tracking and billing for enabled channels. Use the actual parcel dimensions, weight and destination for a U.S. parcel comparison. Compare U.S. parcel shipping options

Warehouse labeling FAQ

Yes, if the system supports client-scoped identity and resolves the task to the correct client. Check the actual uniqueness rule and a wrong-owner test before enabling it.

Yes, when the supported task resolves it to the right item and packaging unit within the owner context. Test the physical label and posting in each intended workflow.

Use a validated packaging record or explicit unit selection, with a verified factor and one conversion point. Check the posted quantity in the task’s base unit.

Remove the old active symbol at the cutover and verify the new one in the real task. If a supported alias is needed, document its target and expiry and test both codes.

A read can succeed while the task rejects the record, unit or quantity. Check the decoded string, lookup result, task context and confirmation history.

The tote ID follows the warehouse handling unit and its assignment. The tracking number follows the transport record. Link them where the workflow requires the relationship.

Sources and methodology

Sources reviewed November 12, 2026. Vendor features apply to the named product and documentation. The SOP, formulas and controls are suggested operating procedures. The fictional cases use teaching assumptions for quantities, times and costs.