Jobs to be done guide for Logentic Tools

Last updated: May 12, 2026

Jobs to be done guide for Logentic Tools

This guide explains Logentic Tools by the jobs an operator, brand, 3PL, supervisor, or counter is trying to complete. Use it when you are not sure which section of the app to open, what output you need, or how one step connects to the next.

Logentic Tools is project-based. It does not replace live inventory in the WMS. Its purpose is to help a brand or 3PL create a clean launch snapshot before go-live: product data, warehouse locations, labels, physical counts, exceptions, supplies, and export files.

Job 1: Prepare a brand for Logentic onboarding

When you need to do this

Use this job when a brand is moving from another system, launching with Logentic, changing warehouse process, or preparing a client onboarding project.

Use this when

  • The brand has product data in Shopify, ShipStation, Extensiv, Google Sheets, or another system.
  • The warehouse needs location labels before the count.
  • Staff need to walk the floor and verify inventory.
  • The final output needs to be imported into Logentic or handed to the implementation team.

Before you start

  • Confirm the brand or client name.
  • Confirm whether the account is a brand account or 3PL account.
  • Gather the product catalog export.
  • Gather any existing SKU, UPC, barcode, inventory, and location files.
  • Decide who owns product data, warehouse layout, label printing, counting, review, and final export.
  • Make sure the warehouse has enough scanners, tablets, printers, computers, label stock, carts, and Wi-Fi coverage.

Recommended steps

  1. Open Home to see onboarding status across the whole project.
  2. Open Onboarding and complete the brand profile.
  3. Open SKU & UPC and upload the product catalog.
  4. Clean SKUs, fill UPCs, and export a Shopify-ready or WMS-ready product file.
  5. Open Warehouse Layout and build the physical layout.
  6. Define the location naming convention.
  7. Open Labels or print labels from the selected racks in Warehouse Layout.
  8. Place the location labels in the warehouse.
  9. Open Team and invite supervisors and counters.
  10. Open Inventory Mapping and upload the SKU or expected inventory list.
  11. Counters scan locations, scan UPC/SKU values, enter quantities, and save progress.
  12. Supervisors review progress, duplicates, unknown UPCs, zero quantities, and missed locations.
  13. Export product, location, mapping, count, and exception files.

What good looks like

  • Every sellable product variant has a usable SKU.
  • Every sellable product variant has a UPC or barcode when required.
  • Every physical pickable location has a unique location code.
  • Location labels are printed, placed, and scannable.
  • The count is tied to a saved project and can resume later.
  • Supervisors can see who counted what, where, and when.
  • Exceptions are reviewed before import.
  • Final exports are clean enough for the implementation or WMS team.

Outputs

  • Brand onboarding profile.
  • Product master CSV.
  • Patched Shopify CSV when applicable.
  • SKU and UPC data quality report.
  • Warehouse layout project file.
  • Location master CSV.
  • Location label PDF.
  • Aisle sign PDF.
  • SKU-location mapping CSV.
  • Inventory count CSV.
  • Exceptions CSV.
  • Supplies buying plan.

Common issues

  • Product catalog does not include UPCs. Upload the best available product list, then use SKU & UPC to fill or assign missing codes.
  • Warehouse layout is not ready. Build a simple layout first, print labels, then refine the map later.
  • Staff count before labels are placed. Stop and place location labels first, otherwise the count will be harder to validate.
  • Multiple users are counting the same location. Use supervisor progress and worker activity to identify duplicates and recount needs.
  • A counter scans an unknown UPC. Keep the scan as an exception instead of discarding it.

Job 2: Clean Shopify SKU and UPC data

When you need to do this

Use this job when the brand has messy SKUs, missing UPCs, duplicate barcodes, inconsistent variant naming, or a Shopify export that cannot be safely imported into the WMS.

Before you start

  • Export products from Shopify.
  • Include all variants.
  • Keep the original file untouched.
  • Confirm whether existing SKUs should be preserved, overwritten, or used as a base code.
  • Confirm the desired SKU nomenclature.

Recommended workflow

  1. Open SKU & UPC.
  2. Upload the Shopify product export.
  3. Review the preview rows.
  4. Choose the SKU pattern.
  5. For customer-specific rules, add the product or brand prefix. Example: One Bone may use a base like OB284 instead of only OB.
  6. Choose whether existing SKUs are preserved or rebuilt.
  7. Assign missing UPC or barcode values.
  8. Preview the full CSV.
  9. Review warnings for duplicates, missing fields, or invalid barcode values.
  10. Download the patched Shopify CSV.
  11. Download UPC labels if the warehouse needs physical product barcode labels.

What good looks like

  • Generated SKUs are predictable and readable.
  • Variants are uniquely identified by style, color, size, and version.
  • UPCs are present for every variant that needs one.
  • Existing brand-approved SKUs are not overwritten accidentally.
  • The downloaded CSV can be uploaded back to Shopify or used for WMS setup.

Example SKU pattern

For One Bone, a pattern could follow this structure:

OB284-Gender-Type-Style-Color-Size-Version

The exact code should be confirmed with the brand before export.

Outputs

  • Shopify-ready patched CSV.
  • Product master CSV.
  • UPC assignment list.
  • Data quality report.
  • Printable UPC labels.

Common issues

  • Existing SKUs are actually style codes, not variant SKUs. Use them as a base value, then append variant tokens.
  • Shopify option names do not match expected tokens. Review the preview before export.
  • UPC values have leading zeroes. Keep them as text and do not open the CSV in a spreadsheet tool that strips leading zeroes.

Job 3: Build a warehouse layout

When you need to do this

Use this job when you need a digital representation of the warehouse before labeling, inventory mapping, or launch planning.

Before you start

  • Measure or estimate warehouse length and width.
  • Identify dock doors, pack stations, staging, returns, value-add, offices, obstructions, walls, and rack rows.
  • Decide whether the layout needs to be approximate or dimensionally accurate.
  • If available, upload a floorplan image or PDF as an underlay.

Recommended workflow

  1. Open Warehouse Layout.
  2. Enter warehouse dimensions.
  3. Add dock doors, pack stations, returns, staging, value-add, offices, columns, walls, conveyors, and custom zones.
  4. Add racking rows, shelving, pick faces, or pallet rack.
  5. Drag and resize elements until the layout matches the floor.
  6. Use copy/paste for repeated rack rows.
  7. Use multi-select to move related elements together.
  8. Use the hand tool to pan the map.
  9. Switch to big canvas mode for detailed layout work.
  10. Add pick paths with start and end points, such as carts to pack station.
  11. Open 3D mode to validate height and vertical storage.
  12. Save the project.

What good looks like

  • The layout is close enough that workers recognize the real warehouse.
  • Core areas are named in plain language.
  • Racks use correct aisle, bay, level, pick face, and pickable level settings.
  • Dimensions are visible enough to validate scale.
  • Layout project is saved and can be exported or imported.

Location naming guidance

  • An aisle is usually the walking path or zone identifier.
  • A bay is a vertical section within the racking across all levels.
  • A level is the vertical shelf or beam level.
  • A pick face or slot is the exact pickable face within a bay.
  • If upper levels are replenishment only, set the exact number of pickable levels.
  • If the physical location does not use pick faces, do not include pick face tokens in the printed label pattern.

Outputs

  • Saved warehouse layout.
  • Exported project file.
  • Location master list.
  • Rack-specific labels.
  • Map export.
  • Pick path reference.

Common issues

  • Two aisles have the same code. Duplicates can be allowed during drafting, but review before printing labels.
  • Location count looks wrong. Check bays, levels, pick faces per bay, and pickable level mode.
  • Text disappears on tiny elements. Resize the element or rely on the inspector and export labels for detailed information.

Job 4: Create and print location labels

When you need to do this

Use this job when warehouse locations need scannable physical labels before inventory mapping or go-live.

Before you start

  • Decide the naming convention.
  • Confirm label stock size.
  • Confirm whether labels need barcodes, QR codes, arrows, titles, or subtitles.
  • Print a small test batch.
  • Test scanning with the actual device that counters or pickers will use.

Recommended workflow

  1. Open Labels or select a rack in Warehouse Layout.
  2. Choose location labels.
  3. Enter the prefix and dimensions, or paste a custom list.
  4. Choose the label size.
  5. Enter title and subtitle if needed.
  6. Adjust location text size.
  7. Choose barcode, QR, or no scan code.
  8. Adjust scan code size.
  9. Add up or down arrows when labels indicate vertical direction.
  10. Preview the label.
  11. Download the PDF.
  12. Print a small batch.
  13. Scan test labels.
  14. Print the full batch.

What good looks like

  • Text is readable from the expected distance.
  • Barcode or QR code scans reliably.
  • The printed label matches the physical location.
  • Labels are centered on the stock.
  • No browser headers or footers are printed.

Supported label types

  • Sheet labels.
  • 3 x 2 labels.
  • 4 x 6 rack/location labels.
  • 60 mm x 40 mm thermal labels.
  • Aisle signs.
  • Custom labels with barcode or QR code.

Mac printing tips

  • Use 100% scale for thermal labels.
  • Turn off headers and footers.
  • Use the printer setting that centers content on the label stock.
  • Avoid fit-to-page when it distorts barcode size.

Common issues

  • QR code looks broken or too small. Increase scan code size or use a larger label.
  • Barcode numbers are above the barcode. Use the UPC label settings where numbers print under the barcode.
  • Labels repeat unexpectedly. Check whether pick face settings are included in the label pattern.

Job 5: Map inventory on the floor

When you need to do this

Use this job when the team needs to verify physical inventory before launch. This is designed for project-based onboarding counts, not live inventory control.

Before you start

  • Make sure location labels are placed.
  • Upload the product list with SKU and UPC if available.
  • Upload expected inventory if available.
  • Invite counters.
  • Assign zones or starting areas.
  • Confirm scanners, tablets, Wi-Fi, chargers, and backups are ready.
  • Explain that the count is blind: counters should count what they see, not what the system expects.

Supervisor workflow

  1. Open Inventory Mapping on desktop.
  2. Select the saved warehouse layout.
  3. Upload the SKU/UPC list.
  4. Upload expected inventory if available.
  5. Create or verify the shared count session.
  6. Invite counters.
  7. Open analytics to monitor progress.
  8. Review scan velocity, top locations, worker activity, duplicates, unknown UPCs, zero quantities, and missing locations.
  9. Export progress regularly during long counts.
  10. Review exceptions before final export.

Counter workflow

  1. Open the scanner view on phone or tablet.
  2. Scan the location label.
  3. Scan every UPC or SKU found in that location.
  4. Enter or confirm quantity.
  5. Save the row.
  6. Repeat until the location is complete.
  7. Confirm moving to the next location.
  8. Continue with the next physical location.

What good looks like

  • Every scan is saved with worker, timestamp, location, SKU, UPC, and quantity.
  • Counters can stop and resume.
  • Supervisors can see progress without interrupting the floor team.
  • Unknown UPCs are retained for review.
  • Duplicate counts are visible.
  • The final export reflects a clean physical snapshot.

Failsafes

  • Local progress autosave.
  • Server-side scan events for shared sessions.
  • Worker and timestamp on each scan.
  • Export progress before the count is done.
  • Unknown UPCs are not discarded.
  • Locations can be reviewed before closing the project.

Outputs

  • SKU-location mapping CSV.
  • Inventory count CSV.
  • Unknown UPC report.
  • Duplicate scan report.
  • Zero quantity report.
  • Worker progress report.
  • Final launch inventory snapshot.

Job 6: Plan supplies for a warehouse launch

When you need to do this

Use this job when a brand or 3PL needs to know what to buy before labeling, counting, packing, and launching.

Before you start

  • Enter order volume, pack stations, pickers, counters, dock doors, locations, rack rows, warehouse square footage, and launch timeline.
  • Load the latest warehouse layout if it exists.
  • Import an existing supply order list if the team already purchased equipment.

Recommended workflow

  1. Open Supplies.
  2. Load the latest warehouse layout or enter operating profile manually.
  3. Review recommended hardware, labels, picking supplies, packing supplies, receiving equipment, and safety supplies.
  4. Compare imported equipment against recommendations.
  5. Adjust buy quantities.
  6. Open supplier links for each item.
  7. Export the plan CSV.

Core categories

  • Hardware: pack station computers, supervisor laptop, scanners, tablets, charging stations, network kit.
  • Labels: thermal label rolls, aisle sign paper, sleeves, test stock.
  • Picking: carts, mobile shelving, shelf bins.
  • Packing: printers, scanners, monitors, scales, pack station peripherals.
  • Receiving: inspection tables and inbound handling surfaces.
  • Safety: floor tape and zone markers.

What good looks like

  • Every counter has access to a scanner or tablet.
  • Every pack station has a computer, scanner, printer, and scale access.
  • The network works on the floor, not only in the office.
  • There is enough label stock for testing and final printing.
  • Supervisors have a workstation for imports, exports, and exceptions.

Outputs

  • Supplies recommendation list.
  • Buy quantity by item.
  • Estimated budget.
  • Imported list comparison.
  • Exported supplies plan CSV.

Job 7: Invite and manage the team

When you need to do this

Use this job when multiple people need access to the same onboarding, inventory mapping, or layout project.

Roles

  • Admin: manages workspace, invites users, exports files, and configures the project.
  • Supervisor: manages inventory mapping, reviews progress, and exports reports.
  • Counter: uses the simplified scanner view to scan locations, UPCs, SKUs, and quantities.
  • Viewer or support role: reviews project context without changing critical setup.

Recommended workflow

  1. Open Team.
  2. Invite users by email.
  3. Assign the correct role.
  4. Ask counters to open the mobile scanner flow.
  5. Confirm each user is in the correct workspace before counting starts.

What good looks like

  • Users only see their own workspace data.
  • Counters do not need to navigate the full app.
  • Supervisors can identify who counted each row.
  • Admins can remove or change access after the project ends.

Job 8: Troubleshoot a launch project

Product data issues

  • Missing SKUs: use SKU & UPC to generate or patch them.
  • Missing UPCs: upload a catalog with UPCs or assign new values.
  • Duplicate SKUs: review the preview before exporting.
  • Leading zeroes missing: keep barcode values as text.

Layout issues

  • Wrong location count: check bay, level, pick face, and pickable level settings.
  • Duplicate aisle names: allowed during drafting, but review before printing.
  • Cannot pan: use the hand tool.
  • Need more room: open big canvas mode.

Label issues

  • QR code too small: increase scan code size.
  • Text too large: reduce text size or use a larger stock.
  • Labels not centered: use printer centering and 100% scale.
  • Repeated labels: check whether hidden pick face expansion is enabled.

Inventory mapping issues

  • Counter cannot log in: verify invite and workspace.
  • Scan does not match SKU: verify UPC exists in uploaded product list.
  • Progress missing: check local autosave, shared session, and current workspace.
  • Duplicate count: review worker, timestamp, and location.

Supplies issues

  • Recommendations feel high: load the latest layout and adjust counters, pack stations, and locations.
  • Imported list does not match: check product names and comments so the matching terms are recognizable.
  • Computers are missing: review the Hardware tab.

Job 9: Export the final launch package

When you need to do this

Use this job when the brand is done preparing and the implementation team needs final files.

Final checklist

  • Product catalog reviewed.
  • SKU and UPC issues resolved or documented.
  • Warehouse layout saved.
  • Location labels printed and placed.
  • Inventory mapping complete.
  • Exceptions reviewed.
  • Supplies plan exported if needed.
  • Team access reviewed.

Recommended export package

  • Product master CSV.
  • Shopify patched CSV if applicable.
  • Location master CSV.
  • Warehouse layout project JSON.
  • Map export.
  • SKU-location mapping CSV.
  • Count result CSV.
  • Exception report.
  • Supplies plan CSV.
  • Notes for implementation team.

What good looks like

The final package should allow another person to understand what was counted, where it was counted, what data was changed, what exceptions remain, and what should be imported next.