feat: Add bulk upload instructions for hard counts, clarify cycle count reject actions, and detail session management actions.

Author: dt2patel

documents/retail-operations/inventory/cycle-count/bulk-upload.md

@@ -44,6 +44,16 @@ After uploading your CSV, map each column to the correct system field so values
      
 * After mapping successfully, click `Submit` to begin processing.
 
+## Creating Hard Counts with bulk upload
+
+Hard counts are created from the same CSV flow. To avoid missing-product errors when you don’t want to preload item lines:
+
+1. In your CSV, set `purposeType` to `HARD_COUNT` for the rows you want to create as hard counts.  
+2. During field mapping, choose `Skip` for the product identifier field (`productSku`). This tells the uploader not to look for item rows when building the count.  
+3. Map the remaining required fields (for example, `countImportName`, `facility`, `estimatedStartDate`, `estimatedCompletionDate`) and submit.  
+
+The uploader will create a hard count with no product list preloaded, so the count opens as a blank, full physical count in the app without throwing a missing-product error.
+
 ## Recently uploaded counts
 
 Below the `Submit` button, you’ll find the recently uploaded counts section. This displays all bulk uploads along with their processing status.

documents/retail-operations/inventory/cycle-count/closed.md

@@ -12,7 +12,7 @@ The `Closed` page in the Cycle Count app lets you review every cycle count that
 
 1. Open the Cycle Count app. Use the navigation drawer on the left side of the screen.  
 
-2. Select `Closed` from the menu. The Closed Counts view displays all cycle counts that have been completed (previously known as “cycle counts history”).  
+2. Select `Closed` from the menu. The Closed Counts view displays all cycle counts that have been completed.  
 
 3. The main pane shows a list of closed counts along with filters at the top. Each row corresponds to a completed cycle count and shows the count name, ID, facility, created date and closed date.
 

documents/retail-operations/inventory/cycle-count/pending-review.md

@@ -150,7 +150,7 @@ Each item row contains the following information:
 3. **Actions**  
 
 * `Accept`: Approve the counted quantity.  
-* `Reject`: Reject the count and send the item for recount.
+* `Reject`: Mark the item as rejected; the counted variance is skipped and the system quantity stays unchanged.
 
 Note: Bulk actions can be applied when multiple items are selected using the checkboxes.
 
@@ -159,7 +159,7 @@ Note: Bulk actions can be applied when multiple items are selected using the che
 At the top of the item list, you can perform bulk actions for all selected items:
 
 * `Accept`: Accepts the counted quantities of selected items.  
-* `Reject`: Rejects selected items and sends them for recount.  
+* `Reject`: Marks selected items as rejected so their variances are skipped and system quantities are left as-is.  
 
   Clicking these buttons will apply the chosen action to all selected rows simultaneously.
 
@@ -197,9 +197,9 @@ When the admin clicks `Close count`, the system opens a confirmation modal with
    * Example: If three items are still open and the admin wants to approve them at once, selecting this option completes the review quickly.
 
 2. Reject all outstanding variances and close  
-   * Automatically rejects all remaining open variances.  
-   * Useful when the admin wants those items to be recounted or corrected later.  
-   * Example: If several items show unusual variances, the admin can reject all of them in one action.
+   * Automatically rejects all remaining open variances and keeps system quantities unchanged for them.  
+   * Useful when the admin does not want to apply the proposed variances.  
+   * Example: If several items show unusual variances, the admin can reject all of them in one action to leave inventory as-is.
 
 Closing the cycle count ensures that the cycle count lifecycle is completed and that the inventory updates are accurately reflected in the system.
 

documents/store-operations/cycle-count/start-complete-session.md

@@ -32,6 +32,15 @@ Inside a session, the associate will see:
 * Option to discard the session  
 * `Submit` button for when the session is complete
 
+### Session actions (edit, discard, submit)
+
+* **Edit**: Opens a modal to update the session name and area. Available while the session is `In progress` and not locked by another user.  
+* **Discard**: Shows a confirmation before marking the session as discarded. Available while the session is `In progress` and not locked. Once discarded, the session is removed from review and you are returned to the counts list.  
+* **Submit**: Completes the session. Appears only while the session is `In progress`; disabled when the session is locked. Submission is blocked until all unmatched items are resolved.  
+* **Locked sessions**: If another user/device holds the lock, all action buttons are disabled until the lock is released.  
+* **After submission**: The action bar only shows `Re-open session` (outline, yellow) so you can resume counting if needed.  
+* **Discarded sessions**: The action bar shows a `Session discarded` badge; no other actions are available.
+
 ### Scanning items
 
 The scan action button changes based on session state: