> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-profiles-tab.md). # Profiles Tab Create, organize and manage checkout profiles in Stellar AIO 4.0, including shipping, billing, payment details and imports. The **Profiles** tab stores the contact, shipping, billing and payment details Stellar uses during checkout. Saving these details in a profile lets you select them when creating tasks instead of entering them again each time. This overview explains the main controls in **Stellar AIO 4.0**. Follow your retailer’s guide for any requirements specific to its checkout mode. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2Fcd1ox626nLD4c5KaXPp4%2Fclipboard.png?alt=media\&token=1fb0bb71-a805-4019-a028-9da5af1dde76) Stellar AIO 4.0 Profiles tab with an empty profile group selected *This example uses an empty group so no personal or payment details are displayed.* ### Profiles, profile groups and tasks * **Profile:** One saved set of checkout details, including an email address, phone number, delivery address and payment information. * **Profile group:** A folder that keeps related profiles together. For example, you could use a group named Main Profiles. * **Task group:** A separate collection in the Tasks tab. It contains the jobs Stellar runs for a retailer. Create or select a **profile group** before adding a profile. You do not need to create a task group first. A profile is also different from a retailer account. Some checkout modes use saved account information or payment methods from the retailer’s website. Check the retailer guide to understand which details the mode uses. ### 1. Create a profile group 1. Open **Profiles** in the sidebar. 2. Select the **+** beside **PROFILE GROUPS**. 3. Enter a clear **Group Name**, such as Main Profiles. 4. Select **Add**, then select the new group on the left. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2FgpXlHQZ3pko5CZroOjxz%2Fclipboard.png?alt=media\&token=963843c2-b0b8-4207-a83a-69a6b8ebd6fa) New Profile Group dialog with an example group name The group list also includes **All Profiles** for viewing profiles across groups and **All Expired** for reviewing profiles with expired cards. To add a new profile, select a regular profile group; Add Profile is unavailable in the All Profiles view. ### 2. Add your first profile With a profile group selected, choose **Add Profile**. Complete the form, review the details and select **Save**. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2FSjCaVwkCWS3UtVAmi1FD%2Fclipboard.png?alt=media\&token=dcf67e77-ff4b-4563-827c-8cfadd66e1e5) Blank Stellar 4.0 profile form showing contact, payment, shipping and billing fields #### Profile and contact details * **Profile name:** A label that helps you identify this setup when selecting a profile for a task. * **Email:** The email address to use for checkout where the retailer uses the profile’s contact details. * **Phone number:** Your checkout contact number. Follow any formatting requirements in the retailer guide. #### Payment Information Enter the **cardholder name**, expiration date in **MM/YY** format, **card type**, **card number** and **CVV**. Check these carefully before saving, especially after replacing a card. #### Shipping Information This is where the order should be delivered. Enter the recipient’s first and last name, street address, any required apartment or unit details, country, state, city and postal code. Use Address line 2 when needed for additional delivery details. #### Billing Information This is the address associated with the payment card. Enable **Billing address same as shipping address** only when the two addresses are the same. Otherwise, leave it off and complete the billing fields separately. #### One Checkout Per Profile The **One Checkout Per Profile** option is intended to limit the profile to one checkout for the module. The app states that the limit resets when you **stop all tasks for the module or restart Stellar**. Do not treat it as a permanent lifetime limit or as the number of units to buy in an order. Follow the retailer guide when deciding whether to enable it. ### 3. Use profiles when creating tasks After saving your profiles, open **Tasks**, select the appropriate retailer group and choose **Create Task**. Select the required profile or profiles in the task’s **Profile** selector. Organizing profiles into groups makes it easier to select multiple profiles and create tasks for them. Review the resulting task rows and their assigned profiles before starting. Saving a profile does not create or start a task by itself. See [What is the Tasks tab?](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-tasks-tab) for the current task-creation walkthrough. ### Find and manage existing profiles Use the search box in the group list to find a group, and **Search Profiles** to find profiles in the current view. The view menu lets you switch between **Card View** and **List View**. In Card View, open a profile’s **More actions** menu to find: * **Edit:** Update that profile’s saved details. * **Duplicate:** Make a copy. Review the copy’s name and details before using it. * **Copy to Profile Group:** Place a copy in another group while keeping the original. * **Move to Profile Group:** Organize the profile into another group. * **Export to JSON / Export to CSV:** Save that profile to a file. * **Delete:** Remove the profile. **Show card details** reveals payment information on a profile card. Keep it hidden when sharing your screen or taking screenshots. The group list also offers **Edit**, **Duplicate** and **Delete** controls for groups. Check whether you are acting on a group or an individual profile before making a change. #### Edit All and Delete All **Edit All** opens a bulk editor. Check the **Edit Profiles (number)** heading before entering changes so you know how many profiles are included. Use an individual profile’s Edit action when only one profile needs an update. **Delete All** is for removing profiles from the current group. Review the selected group and any confirmation carefully. Deleting profiles is different from stopping tasks. ### Import profiles **Import** opens a file picker so you can load saved profiles. Stellar supports its own exported profiles as well as supported profile exports from **AYCD** and **Essentials**. 1. Select the profile group you want to work with. 2. Select **Import** and choose your profile file. 3. Review the imported profiles, including names, contact details, addresses, expiration dates and payment details, before using them in tasks. If you want to prepare a CSV file yourself, open the arrow beside **Import** and select **Download CSV Template**. Use that template’s column names and format. If an import fails, check that you selected a supported profile export rather than an unrelated file. ### Export profiles The toolbar’s **Export to CSV** button saves profiles from the current group to a file. Open the arrow beside it for **Export to JSON**. For a single profile, use its More actions menu. Exports let you reuse saved profile information or keep a backup for importing into Stellar later. Store these files privately: they contain sensitive checkout information and should not be posted in Discord or included in public screenshots. ### Before using a profile * Make sure the profile is saved in the group you intended. * Check the delivery address, including apartment or unit details. * Confirm that billing matches the card’s billing address. * Check the card number, expiration date, card type and CVV. * Select the correct profile in your task setup and follow the retailer guide’s account and payment instructions. If a profile is missing from a task’s selector, first check that it was saved and that you are looking in the correct profile group. If checkout fails, review the task’s exact status and retailer guide; a saved profile alone does not confirm that every checkout requirement has been met. ### CSV imports and profile variations For spreadsheet preparation, supported random-value tokens and a full import/export walkthrough, use [How do I Mass Import & Export Profiles](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-profiles-tab/how-do-i-mass-import-and-export-profiles). Importing adds profiles without replacing existing ones. Review a small test import before importing a large file. **J1G** is a community term for variations of a base checkout profile. Members may use these to organize accounts and tasks, but requirements vary by retailer. Stellar does not provide an official J1G spreadsheet, generation formulas or retailer-specific J1G methods; ask your cook group for current guidance. Variations do not guarantee checkouts, prevent cancellations or override order limits. Keep shipping information deliverable and billing/payment details valid. Check emails, phone numbers, country/region and required fields after importing; remove accidental spaces and unresolved spreadsheet formulas. Some account-based retailers require the profile email to match the retailer account. Start small, test the intended setup and keep a private backup. Stellar support can help with CSV formatting, importing and missing profile fields. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-profiles-tab.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.