Setting Up Your First Delivery

Your first delivery is the moment wallmarkets stops being a setup project and starts being an operational system.

That is why the first delivery matters more than most teams expect. It tests whether your products are usable, whether your supermarket records are clean, whether the person creating the delivery understands the workflow, and whether the team can close the job properly once it is done.

The goal is not to make the first delivery perfect. The goal is to make it real.

What needs to exist first

Before you create the first delivery, make sure these three pieces are already in place:

• at least one product in your catalog
• at least one supermarket account with a usable branch record
• a verified account you can sign back into confidently

If any of those are missing, stop and fix them first. A first delivery created on incomplete setup usually teaches the wrong lessons.

Pick the right delivery for your first run

Do not choose the most complicated order in the business.

Pick something normal:

• one familiar supermarket branch
• a manageable number of line items
• a delivery date close enough to matter
• a route the team already understands

The first delivery should prove the workflow, not stress-test it.

Step 1: Confirm the destination carefully

The first thing to get right is the receiving location.

If you supply multiple branches of the same chain, confirm the exact branch and address before you add anything else. Most early delivery mistakes are not product mistakes. They are destination-detail mistakes: wrong branch, old contact, or assumptions carried over from spreadsheet habits.

If the branch detail still feels vague, update it now rather than "fixing it later."

Step 2: Add only the products that are genuinely going out

Choose the products being shipped and enter the actual quantities. Do not pad the first delivery with extras just to see what the interface can hold.

The first delivery is valuable because it becomes the first trustworthy record in the system. Keep it honest:

• use the real product names
• use the real quantities
• use the real target date
• keep the branch and product details specific enough that the team will recognize them later

If you discover missing price, weight, or naming detail while building the delivery, that is useful information. It means the catalog still needs cleanup.

Step 3: Think like the driver and the receiving team

Before you submit, ask two practical questions:

1. If a driver opened this on their phone, would they know exactly where to go and what to unload?
2. If the receiving team questioned part of the delivery later, would the record be clear enough to answer them?

If the answer is no, fix the branch detail or product clarification now.

That habit matters because wallmarkets is not just a planning tool. It is the record you will rely on after the route is done.

Step 4: Submit and treat the detail page as the source of truth

Once the delivery is created, the detail page becomes the place to check what was scheduled, what was included, and what happened next.

This is where teams begin to feel the difference between a system and a spreadsheet. Instead of reconstructing the delivery later, you already have a clean starting record the whole team can work from.

What to do when the delivery is completed

The first delivery is only useful if you also close it properly.

After the route:

• confirm the delivery happened as planned
• record any discrepancy while it is still fresh
• log any return against the original delivery, not in a separate private record

This is the moment many teams slip back into old habits. They create the delivery in the system, then handle the messy part informally. Resist that. The messy part is exactly why the system exists.

What a successful first delivery looks like

You do not need a flawless route to call the first delivery a success.

Success looks like this:

• the destination was correct
• the product list was accurate
• the team could understand the record
• any issue was logged in the same workflow
• someone can now look back and see what actually happened

That is enough to justify the next delivery going through the same process.

What to review afterward

Once the first delivery is finished, spend ten minutes reviewing the record with the person who created it and, if possible, the person who handled it in the field.

Look for:

• product names that were too vague
• branch instructions that should have been recorded
• details that were still too vague once the delivery was in motion
• anything that made the return or discrepancy workflow feel awkward

That short review improves the next delivery much more than adding more documentation no one will read.

Common first-delivery mistakes

Starting with a fake test order

Fake orders are safe, but they often hide the real problems. Real deliveries expose unclear branch data, weak product names, and operational gaps quickly.

Recording the delivery but not the follow-up

If a discrepancy or return gets handled outside wallmarkets, the first record is already incomplete.

Picking the wrong branch because "it looked close enough"

Branch-level detail matters. Treat it as operational data, not background information.

What to do next

After the first delivery is complete, move straight to these pages:

• Create deliveries consistently
• Track deliveries after creation
• Read the dashboard correctly

Once those three feel normal, you are past setup. You are building a real operational history.