STANDING ORDERS

A standing order bills the card on file automatically every cycle, and each successful charge creates a new order here that ships on the normal PLACED → CONFIRMED → SHIPPED → DELIVERED trail. Prices are re-read from your live tier pricing when the standing order is started. Cancel is immediate and never touches orders already placed.

ACCOUNT SECURITY — SET YOUR OWN PASSWORD

If you signed in with a temporary password from Atlas, set your own here (10+ characters).

Operating policies. The terms below govern wholesale ordering. Highlighted values load from the signed supply agreement at activation — where a value is marked, the written agreement controls.

Configuration rule: supplier identity, timing, minimums, shipping, replacement, return, payment, and support terms remain `[SUPPLIER CONFIG]` or `[ATLAS CONFIG]` until loaded from the signed operating terms.

Portal introduction

Headline

One Order. One Status Trail. No Guessing.

Supporting copy

Choose from the approved catalog, review the order, and submit it once. Atlas checks the order for completeness and routes it to `[SUPPLIER CONFIG: supplier or distribution route]`. From there, the portal keeps the order status, tracking, and any exception in one place.

Your business remains the seller and the customer-facing relationship owner. Atlas manages the ordering layer and supplier coordination for Atlas-sourced products; Atlas does not contact your customers directly.

How ordering works

Step 1 — Build the order

Select an approved item, quantity, and delivery method. Current price, availability, supplier minimums, and shipping options appear in the portal before submission. If a field still shows a configuration notice, that item is not ready to order.

Step 2 — Choose the destination

Choose either an approved direct-ship destination or partner-held inventory, when available. If an order ships directly to your customer, your business remains responsible for customer communication before and after delivery.

Step 3 — Review before submitting

Confirm the item, quantity, destination, total cost, shipping charge, and applicable supplier terms. Payment is collected according to `[SUPPLIER CONFIG: payment timing and method]`. Submission means the order enters Atlas review; it does not mean the supplier has accepted or shipped it.

Step 4 — Atlas reviews and routes

The order first appears as **Placed — Atlas Review**. Atlas checks the order against the current catalog and routing requirements. A complete order is routed to `[SUPPLIER CONFIG]`; an incomplete or unavailable order is placed on hold with the next required action shown in the portal.

Step 5 — Follow the status

The normal status path is:

**Placed — Atlas Review → Routed to Supplier → Shipped → Delivered**

Tracking appears after the supplier or carrier issues it. A status is a record of the current step, not a promise of a delivery date.

Step 6 — Report an exception in the portal

If an order arrives damaged, incomplete, incorrect, or otherwise does not match the packing record, use **Report an Issue** from the order detail page. Atlas opens the supplier case and keeps the record attached to the original order. Your team remains the point of contact for your customer.

Fulfillment expectations

What happens after submission

• Atlas review target: `[ATLAS CONFIG: review window]`.
• Supplier acceptance target: `[SUPPLIER CONFIG: confirmation window]`.
• Handling estimate: `[SUPPLIER CONFIG: handling window]`.
• Carrier estimate: `[SUPPLIER CONFIG: carrier and transit window]`.
• Order cutoff, holiday, weather, back-order, and destination rules: `[SUPPLIER CONFIG]`.

These are operating targets and estimates. The portal status and carrier record are the current source for each order.

Holds, changes, and unavailable items

If an item, quantity, destination, or required order detail cannot be accepted, the order moves to **Hold — Action Required**. The portal will show whether the next action belongs to the partner, Atlas, or the supplier. No substitution or material order change is accepted unless the applicable approval is recorded.

Direct ship and partner inventory

Direct ship reduces partner handling but does not transfer the customer relationship to Atlas. Partner-held inventory gives the partner more local control, while the partner remains responsible for storage, inventory counts, expiration monitoring, and unsellable stock. Any supplier return or replacement exception follows `[SUPPLIER CONFIG: inventory and return terms]`.

Damaged, incomplete, or incorrect shipment process

Fast rule

Do not let an exception disappear into email. Attach it to the order.

Report the issue

Submit the issue within `[SUPPLIER CONFIG: reporting window]` and include:

1. order number;

2. affected item and quantity;

3. what was received versus what was expected;

4. photographs of the shipping container, label, packing record, and affected contents when available;

5. lot or batch information when shown; and

6. the requested resolution: missing-item shipment, replacement, credit, or other supplier-supported option.

Keep the shipment and packaging available until the case instructions say otherwise. Do not redistribute an item that appears damaged, opened, mislabeled, or otherwise compromised.

What happens next

Atlas records the case and routes it to `[SUPPLIER CONFIG]`. The portal status changes to **Issue Reported** and then to the applicable resolution state. Available outcomes depend on `[SUPPLIER CONFIG: replacement, credit, return, and shipping terms]`.

The partner handles customer communication and any customer-facing refund decision. Atlas coordinates the supplier record and resolution path; Atlas does not contact the partner's customer directly.

Reorder cadence

Reorder before urgency takes over

The portal may display a reorder reminder based on `[SUPPLIER CONFIG: item cadence]`, prior order timing, or a partner-set reminder. A reminder is a prompt to review—not an automatic order and not a forecast of customer demand.

Before reordering, check:

• current on-hand quantity;
• open and in-transit orders;
• recent usage or sales pace;
• expiration or handling window;
• current supplier availability and minimums; and
• any catalog, price, or shipping changes.

Two supported modes

**Order as needed:** submit approved orders as demand is confirmed.

**Carry inventory:** place larger approved orders and manage stock locally.

The partner chooses the operating mode and carries the inventory, storage, expiration, and unsellable-stock responsibility for partner-held inventory. Supplier-specific exceptions remain `[SUPPLIER CONFIG]`.

Support and escalation

Start with the order record

For the fastest answer, open the order and select the issue type. That gives support the order number, status history, item record, and attachments in one case.

Escalation path

1. **Order status or portal question:** `[ATLAS CONFIG: standard support route and hours]`.

2. **Damaged, incomplete, incorrect, or delayed shipment:** use **Report an Issue** on the order.

3. **Urgent product-integrity or safety concern:** stop normal distribution of the affected item and use `[ATLAS/SUPPLIER CONFIG: urgent escalation route]` immediately.

4. **Unresolved supplier case:** escalate with the case number through `[ATLAS CONFIG: escalation owner and route]`.

Atlas owns the supplier-coordination record. The supplier owns its investigation and supplier-supported remedy. The partner owns communication with its customer.

Support commitment block

You should never have to reconstruct an order from scattered messages. Give us the order number once. We keep the status, evidence, supplier case, and resolution history connected from submission through closure.

Portal microcopy

Primary actions

• `Submit Order for Atlas Review`
• `Review Order Before Submission`
• `Track This Order`
• `Report an Issue`
• `Reorder These Items`
• `View Required Action`

Status explanations

| Status | Partner-facing explanation |

|---|---|

| Draft | Your order has not been submitted. |

| Placed — Atlas Review | Atlas received the order and is checking it for routing. |

| Hold — Action Required | The order needs a listed action before it can continue. |

| Routed to Supplier | Atlas sent the approved order to `[SUPPLIER CONFIG]`. |

| Shipped | Tracking has been issued for this order. |

| Delivered | The carrier reports delivery. Review the shipment promptly. |

| Issue Reported | The exception is recorded and supplier coordination is in progress. |

| Replacement | A replacement was approved under `[SUPPLIER CONFIG: replacement terms]`. |

| Closed | The order or exception record is complete. |

Submission confirmation

**Order received. Atlas review is next.**

Your order is now **Placed — Atlas Review**. We will either route it to `[SUPPLIER CONFIG]` or show the exact action required in the portal. Supplier acceptance, shipping, and tracking follow after review.

Issue confirmation

**Issue recorded. Keep the shipment available.**

Your case is attached to the original order. Atlas will coordinate the supplier record and post the next action or resolution status here. Continue communicating directly with your customer; Atlas will not contact them.

Reorder reminder

**Time to check—not automatically reorder.**

Review your on-hand quantity, open orders, expiration window, and current supplier terms before submitting the next order.

Required configuration before activation

• `[SUPPLIER CONFIG: identity and approved route]`
• `[SUPPLIER CONFIG: catalog, pricing, availability, and minimums]`
• `[SUPPLIER CONFIG: payment timing and method]`
• `[SUPPLIER CONFIG: handling, transit, cutoff, and holiday rules]`
• `[SUPPLIER CONFIG: damaged, short-ship, wrong-item, return, credit, and replacement terms]`
• `[SUPPLIER CONFIG: reporting windows and evidence requirements]`
• `[SUPPLIER CONFIG: urgent escalation and product-integrity route]`
• `[ATLAS CONFIG: review window, support owner, hours, and escalation route]`
• `[ATLAS CONFIG: direct-ship and partner-inventory permissions]`
• `[ATLAS CONFIG: notification and reorder-reminder settings]`

Integration note for Claude Code

The five portal sections requested by Directive 05 are complete: how ordering works, fulfillment expectations, damaged/short-ship process, reorder cadence, and support escalation. The copy is modular so the portal can render a short accordion while notifications reuse the matching confirmation blocks. No catalog, supplier, product, price, timing, or remedy term has been invented.