> ## Documentation Index > Fetch the complete documentation index at: https://help-empuls.xoxoday.com/llms.txt > Use this file to discover all available pages before exploring further. # Company store > Add your own products to the Empuls redemption store and route each product's redemption requests to the person who actually fulfils them. The **Company store** lets you offer your own items alongside the Empuls reward catalogue — branded merchandise, an extra day of leave, lunch with a leader, a parking space. Employees redeem them with points like anything else, and each redemption raises a request for someone to approve and fulfil. It has two tabs: | Tab | What it holds | | - | - | | **Catalog** | The products you have added, and the controls to add or edit them | | **Requests** | Redemption requests waiting on a decision | ## Add a product Adding an in-house item runs through three steps. Name the product, describe it, add images, and set its terms. This is also where you choose **who approves** redemptions of it — see below. Set what the product costs an employee in points. Explain what happens after someone redeems it, so expectations are clear before they spend their points. Product name, description, images and terms stay editable after publishing, so you can correct a description or swap an image without rebuilding the product. ## Route redemptions to the right approver By default every redemption notifies all Super Admins, which means somebody has to forward each request on to whoever actually fulfils it. Instead, set an approver per product. On the **Details** step, choose one of: | Approver | Who gets the request | | - | - | | **Super Admin** | Every Super Admin, the original behaviour | | **HRBP** | The HR business partner of the employee who redeemed | | **Department head** | The head of that employee's department | | **Cost centre head** | The head of that employee's cost centre | | **Business unit head** | The head of that employee's business unit | | **Custom** | Named people you pick | The four relationship-based options — HRBP, department, cost centre and business unit head — resolve **per redemption**, against the employee who redeemed. One parking-space product can therefore route to a different manager for each requester, with no per-site duplicate products. Products where you don't set an approver keep behaving as they did before, notifying Super Admins. You can adopt this product by product rather than all at once. ## Act on requests The **Requests** tab lists redemptions waiting on a decision. Approvers can search and filter by employee ID, department, designation and location before acting, which matters when a popular product generates a long queue. ## Permissions Creating products and approving redemptions are **separate permissions**. Someone can be given the ability to approve the requests that reach them without also being able to add or edit products in the catalogue. Grant them in the role's permission matrix — see [Access control](/admin/user-management/access-control). ## Related Send store products as a gift rather than having employees redeem them. Restrict the store to each employee's tagged country. Set who can create products and who can approve redemptions. What the store looks like to an employee.