Stores ask. Head office answers.
Nothing gets lost.

What goes wrong when stores ask through chat and email

1. Stores ask for supplies, help and approvals in group chats, emails and phone calls.
2. Nobody can tell who owns a request or whether it was ever answered.
3. Requests arrive with missing details, so head office has to ask again.
4. Photos and files get buried in chat threads.
5. Managers can’t see how many requests are open or which stores send the most.

How Bitreport runs store requests

Head office builds each request type as a form: the fields a store fills in, optional resolution fields for the person handling it, who can send it, who receives it, and the statuses it moves through. A store picks the type on its phone, fills in the form with photos or files, and sends it to the right people. It stays open until it is closed with a final status.

Request types are yours to define, such as a supply order, a marketing material order, a request for help, or a notice to head office. Breakdowns and repairs have their own flow in Incident Reports, and when head office is the one asking, for example for a stock count from every store, see Store Supply Counts.

Forms, senders, and receivers you control

Build both the request form and an optional resolution form from short text, long text, number, number with unit, date, option list (single or multiple answers), photo, and attachment fields, and mark the ones that are required. Give each request type a name, a description, a tag with its own supervisors, and a numbering counter (default yearly numbering or your own global or per-branch sequence).

Choose Request Senders and Request Receivers by role, user, or group. For each receiver, turn Notifications and Auto-assign on or off, and optionally allow receivers and assignees to edit submitted form fields if a store made a mistake.

One thread from request to answer

Every request has a status, assignees, comments, and an activity history that shows who submitted the request, who changed the status, who was added or removed as assignee, and when form or resolution fields were updated. Choose statuses such as Submitted, In Progress, Completed, Approved, or Denied, or create your own, with a default for new requests and final statuses that close them.

Any receiver or supervisor can claim an unassigned request with Assign to me or assign it to a colleague. Assignees can move a request through every status and fill in the resolution form, while the sender can also mark their own request as completed. People get a notification when a request is received, assigned, commented on, resolved, or changes status, and each person can choose to get these notifications on WhatsApp too. Any request can be downloaded as a PDF.

Every request, every store, one list

See all requests in one list, switch between all, sent, received, and archived, and group them by tag, status, date, assignment, or request type. Filter by tag, request type, sender, assignee, status, branch, or date, and by the value of a form field, or show form fields directly as columns in the table.

Change the status of several requests at once, archive them, or export the list to Excel with an option to bundle all photos and files into a ZIP archive. On their phones, stores see the requests they sent, filter by status, and read comments and updates in real time.