The fastest way to stand up a warehouse in a WMS is to import your storage locations and starting pallets from an Excel file instead of keying them in one at a time. Shipider takes a single spreadsheet upload and turns it into a live site, with your aisles, bays, and location types feeding the rack map and your pallets landing in the right spots. If your operation already runs on spreadsheets, that setup can take minutes rather than an afternoon of manual data entry.
Most warehouses that outgrew paper and email did not start with a clean database. They started with a workbook that someone maintained by hand, tab by tab, and it worked well enough to run the floor. Shipider is built for exactly that starting point. You do not throw away the sheet you already trust. You bring it with you.
What you can import
The import covers the two things you need before a warehouse can do any real work: the places you store inventory and the inventory itself. Both come from Excel, and both feed directly into what your team sees on screen.
Storage locations that build the rack map
Your storage locations are the skeleton of the site. When you import them, you are describing the physical shape of the warehouse: the aisles, the bays within each aisle, and the location types that tell Shipider what each spot is for. That structure is not just a list in a database. It feeds the rack map, so once the import finishes you can look at a visual layout that matches the building instead of squinting at coordinates.
Getting this right up front matters because everything downstream leans on it. Putaway, picking, and the way pallets are grouped all depend on locations existing and being typed correctly. Defining them in a spreadsheet lets you lay out a whole zone in the rows you already know how to edit, then bring it in as one structured set.
Pallets and their location assignments
Once the locations exist, you import the pallets and where each one sits. This is how you seed a site with real starting inventory rather than an empty shell. Each row ties a pallet to a location, so after the import your rack map is not just a diagram of empty racking. It reflects what is actually on the floor right now.
That pairing of locations first, then pallets, is the natural order, and it is worth respecting because a pallet assignment only makes sense if the location it points to already exists. We will come back to that sequence when we talk about preparing the file.
What the import respects
A bulk upload is powerful, which is exactly why it needs guardrails. The point of importing is speed, but speed without limits is how a single bad file rewrites the wrong part of your warehouse. Shipider applies the same rules to an import that it applies to a person clicking through the interface, so a bulk operation cannot become a bulk mistake.
- Warehouse scope. The import lands inside the warehouse you are working in. It does not spill into other sites. If you run several facilities, an upload aimed at one building stays there.
- The running user's permissions. The import can only do what the person running it is already allowed to do. If a user cannot create locations or move pallets by hand, they cannot do it through a spreadsheet either. The file does not grant new powers; it just applies the ones you have, faster.
- Multi-tenant isolation. Because Shipider keeps every company's data separate, an import is contained to your tenant. Your locations and pallets stay yours.
The practical result is calm. You can hand the import to the person who owns a zone, knowing the system will hold them to the same boundaries they already work within.
Preparing a clean file
A good import starts with a good sheet, and the good news is you probably already have one. You do not need to build a file from scratch or learn a new format. Start from the workbook you keep today and shape it to match what the import expects.
- Start from your existing sheet. Open the workbook your team already maintains. The columns you use to track aisles, bays, and pallets are the raw material. You are reshaping, not reinventing.
- Match the columns. Line up your headers with the fields the import reads, so an aisle is read as an aisle and a location type is read as a type. Clear, consistent headers save you from fixing rows one at a time later.
- De-duplicate. Remove repeated rows and conflicting entries before you upload. A spreadsheet that grew by hand tends to accumulate duplicates. Cleaning them now means the rack map comes out clean.
- Import locations first, then pallets. Bring in the storage locations so the structure exists, confirm it looks right on the rack map, then import the pallets that reference those locations. This order keeps every pallet assignment pointing at a location that already exists.
Spending a few minutes on the file is what makes the setup itself take only minutes. A tidy sheet in means a trustworthy site out. If you want the fuller picture of why a structured system beats a workbook once you are live, the case for moving on is laid out in WMS vs spreadsheets.
Manual entry versus Excel import
The difference between typing a warehouse in and importing it is not only about the first day. It shows up again every time you need to make a large change. Here is how the two approaches compare across the things that actually cost you time and cause errors.
| Consideration | Manual entry | Excel import |
|---|---|---|
| Time to go live | Slow; each location and pallet entered one screen at a time | Fast; a whole site defined in one upload |
| Error risk | Higher; repetitive typing invites slips that are hard to spot | Lower; you review the file once, then it applies consistently |
| Later bulk changes | Painful; adding a zone or a customer's stock means many manual steps | Straightforward; edit the sheet and re-import within scope |
| Reviewability | Scattered across many screens | All in one file you can check before it touches the site |
| Who can safely do it | Whoever has the patience for the clicks | Anyone with the right permissions, held to their scope |
The honest read is that manual entry is fine for a handful of locations and a bad idea for a real facility. Import is the difference between an afternoon and a coffee break.
Using import for ongoing changes
Import is not a one-time setup trick you use once and forget. It is the same tool you reach for whenever the warehouse changes in bulk, and warehouses change constantly. The moments where it earns its keep tend to look like this:
- Opening a new zone. When you add racking or reorganize a section, describe the new aisles, bays, and location types in a sheet and bring them in. The rack map grows to match the building.
- Onboarding a new customer's inventory. If you run a facility that stores stock for multiple customers, a new account can arrive with a lot of pallets at once. Import lets you seed all of them and their assignments in a single pass instead of receiving each one by hand.
- Restructuring after a change. When location types shift or a zone is repurposed, an edited sheet re-applies the new layout within the warehouse and permission scope you already have.
Because every one of these imports still respects warehouse scope and the running user's permissions, a big change stays as safe as a small one. You get the speed of bulk without the exposure of an unchecked bulk edit.
Keeping the site accurate afterward
Getting the warehouse stood up is the start, not the finish. A site is only useful while it keeps matching the floor, so the habits that follow the import are what keep it honest.
Day to day, that accuracy comes from how work is captured. Browser camera barcode scanning lets your team confirm pallets and locations with the device already in their hand, so movements get recorded as they happen rather than reconstructed later from memory. And Shipider's maker-checker workflow means significant changes get a second set of eyes before they are final, which keeps a rushed edit from quietly drifting the records away from reality.
The receiving side deserves its own attention, because inventory that arrives is where accuracy is either built or lost. If you want your imported starting point to stay clean as new stock comes in, it helps to have a disciplined intake routine; the receiving-to-put-away flow covers how to keep that first touch tidy. Pair a clean import with a clean receiving habit and the site tends to stay trustworthy on its own.
Usage-based pricing means the system scales with what you actually run, so growing into more locations, more pallets, and more scanning does not force a decision between accuracy and cost. You keep the site as detailed as the floor demands.
Frequently asked questions
How long does it really take to set up a warehouse with Excel import?
Most of the effort is in preparing a clean file, and if you start from the workbook you already keep, that is a matter of matching columns and removing duplicates. The upload of locations and then pallets is quick, which is why a well-prepared sheet can bring a site live in minutes rather than an afternoon of manual entry.
Do I need to import locations and pallets separately?
Import your storage locations first so the structure exists and the rack map is built, then import your pallets with their location assignments. Each pallet assignment points at a location, so the location has to be there first. Doing it in that order keeps every assignment valid.
Can an import affect the wrong warehouse or exceed my permissions?
No. Every import stays within the warehouse you are working in and can only do what the running user is already allowed to do. If you cannot create a location or move a pallet by hand, the import will not let you do it either. The file applies your existing permissions; it does not expand them.
Is Excel import only for initial setup?
No. It is the same tool you use for ongoing bulk changes, such as opening a new zone or onboarding a new customer's inventory. Edit the sheet and re-import, and the change applies within your scope, so a large update stays as safe as a small one.
How do I keep the site accurate after the import?
Capture work as it happens with browser camera barcode scanning, let the maker-checker workflow review significant changes before they are final, and keep a disciplined receiving routine so incoming stock does not drift from the records. Those habits keep your imported starting point matching the floor over time.
Ready to turn your spreadsheet into a live warehouse? Create your Shipider account and import your first site in minutes.
Related reading: ERP Sync Without Double Entry: Connecting Your WMS to Your ERP