> For the complete documentation index, see [llms.txt](https://help.refractbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.refractbot.com/introduction-to-botting/profiles.md).

# Profiles

A profile is the shipping, billing, and payment information Refract uses to complete a checkout. Profiles are stored locally in the bot.

{% hint style="info" %}
**This page is background, not a setup guide.** We do not assist with profile generation or jigging, and we do not recommend tools or services for it. For that, ask your cook group.
{% endhint %}

## Why people run multiple profiles

Many retailers limit orders to one per customer and use pattern detection to group orders that look like they come from the same person. Because of that, users who want more than one checkout typically run multiple profiles with variations in their details.

How far to vary them, and what each retailer currently tolerates, is community knowledge that changes constantly. There is no setting in Refract that controls this.

## What about jigging?

Jigging means altering profile details (name, address, email, payment method) between orders so retailers do not group them as duplicates. It is a real and common practice in the community.

It is also something we do not help with. We do not teach jigging methods, we cannot tell you whether your jig is good, and we cannot troubleshoot orders that were canceled because of how a profile was jigged. What works varies by retailer and changes without notice.

{% hint style="info" %}
**Start with your cook group.** Users compare notes in Discord communities and cook groups to learn which profile and jigging strategies are currently working. Aside from trial and error, these communities are the best source of up-to-date information, since effective methods are often shared privately.
{% endhint %}

## General practices

We cannot tell you how to jig, but a few practices are stable enough to count as community consensus:

* Use a different email for each profile.
* Use a different payment method for each profile where you can. Virtual card services exist for exactly this; your cook group can tell you which ones members currently use.
* Do not run multiple tasks with identical profile information on sites with order limits. That is the fastest way to get orders grouped and canceled.
* Keep every variation deliverable. Whatever you change, the package still has to reach your address.

Treat these as a floor, not a strategy. The retailer-specific details on top of them are cook group territory.

## Cancellations

Cancellations tied to profiles are almost always caused by retailer-side order checks on your profile, account, proxy, or payment method rather than a setting in Refract. The Refract team can review our logs for signs of a bot-side issue, but we cannot diagnose or resolve retailer-side cancellations, and there is no single change or guaranteed fix that works for everyone.

For a concrete example of how this plays out on Target, see the cancellation section of the Target release guide:

{% content-ref url="/pages/ZFqpmTnmbrPInDm80k4P" %}
[Target Release Guide](/modules/target/target-release-guide.md)
{% endcontent-ref %}

## Setting up profiles in Refract

Creating and importing profiles in the bot itself is covered in the setup guide:

{% content-ref url="/pages/tUHKhiM7oT9qlMeK39c8" %}
[Profiles](/general-setup/profiles.md)
{% endcontent-ref %}


---

# 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://help.refractbot.com/introduction-to-botting/profiles.md?ask=<question>&goal=<user_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.