Is the file public in the channel?
No. Delivery is a DM after PayPal capture.
Direct answer
Distinguish original development resources from Roblox platform purchases. Cartcord can deliver independently licensed source files or documentation where the product and platform rules permit it, but it does not sell Robux, create native Developer Product receipts or grant restricted asset permissions. Use Roblox's required purchase and receipt systems for platform entitlements. Describe file formats, dependencies, ownership, support and the actual delivery method before offering an eligible resource.
How it works for Roblox sellers
- 01
Invite the bot
Open the dashboard with Manage Server.
- 02
Publish the product
Review payment eligibility and configure direct file download or a private link.
- 03
Buyers use /buy
After payment verification, configured delivery is attempted.
Understand the operating cost
Choose by the actual product, audience and services you need. Cartcord's plans are Free $0, Basic $29.99, Pro $59.99 and Enterprise $129.99 per month. Cartcord charges no sales commission; PayPal processing and other merchant costs remain separate. A marketplace may provide discovery, billing, hosting or tax services that a flat Discord-store plan does not.
What a buyer would see
- Low-poly map pack$14.99 · Direct file download or a private link
- Combat system file$29.99 · Direct file download or a private link
What /products shows
Interactive example. This preview does not create an order or charge a payment.
Members open the storefront, choose a product, and start checkout.
Identify whether the product belongs in the Creator Store
Roblox's Creator Store provides a platform workflow for distributing assets and selling eligible models or plugins. Review that workflow and its requirements before choosing an independent sale. A source-art archive, a restricted uploaded asset and a Developer Product inside an experience are not interchangeable. The fact that all three are described as digital assets does not mean the same payment or delivery process can serve them.
If you offer an independently licensed resource, specify the actual files and the rights you can grant. A buyer may need editable source art, textures, documentation or a configuration example rather than a native inventory entitlement. Explain how the resource is imported and which permissions remain controlled by Roblox. A file download cannot override platform asset privacy or automatically add a restricted asset to another creator's inventory.
Package resources that can be reviewed safely
List the file formats, supported Studio environment, object structure, texture requirements and any dependencies. Include an example project or a documented import sequence where appropriate. Tell the buyer whether scripts are included and what they do. Remove unrelated code, private endpoints, credentials and development shortcuts before distribution. The buyer should be able to distinguish a visual asset from a plugin that executes code in the editor.
Use original work or material you are authorized to redistribute. Identify third-party dependencies and whether the buyer must obtain them separately. Do not imply ownership of a popular game's assets, a brand's characters or another creator's scripts merely because they appeared in a demonstration. Keep the license and preview consistent with the files actually delivered, and retain the release version associated with the listing.
Keep Developer Product receipts on the platform
Roblox Developer Products have their own purchase and receipt-processing system. An external PayPal capture is not a native Roblox receipt and must not be represented as one. Cartcord's game-server command delivery and verified Roblox account linking are not released. Do not advertise that purchasing an external listing automatically grants game currency, a pass or an experience-specific benefit through an integration that does not exist.
A typed username or numerical user ID does not by itself establish that the purchaser controls the account. If a future permitted integration requires identity linking, it needs an authorized verification process and server-side receipt handling appropriate to the platform. Keep those responsibilities separate from delivering an original resource file. A checkout confirmation proves only the transaction state recorded by its payment provider.
Demonstrate compatibility without inventing a result
Show the resource in a clean sample environment and explain what the demonstration includes. State performance assumptions and any manual setup required. A polished video may use lighting, animations or other assets that are not part of the purchased package; name those dependencies. If your product is a template, explain which content the buyer is expected to replace and what they must build themselves.
Do not promise a particular audience size, revenue result or game approval. The creator remains responsible for the experience and its compliance with current platform requirements. Keep a changelog when Studio behavior, asset permissions or a dependency changes. Test an update with a copy of the sample project before telling existing buyers that it is compatible with their live work.
Provide a clear support and recovery route
For an eligible independent resource, use the configured file, link, key or manual delivery that matches the offer. Protected uploads can provide authorized downloads on eligible plans, but they cannot enforce every downstream copy or native asset permission. Explain the recovery path and the exact Discord identity used at checkout so a buyer can find an eligible purchase again.
Ask for an order ID, resource version and sanitized reproduction steps when investigating a problem. Do not request an account password, session cookie or an entire private experience export through a public ticket. Review payment and delivery evidence without treating a successful DM as proof that the resource loaded correctly in Studio. Where a platform entitlement is involved, use the appropriate Roblox records and support process instead.
A launch checklist you can repeat
Start from a hidden product and review it as a buyer: name, current price, included deliverables, dependencies, access duration, license and support contact. Connect the seller payment account for the intended store and verify that the selected product can be published. Use a genuine preview of your work. Remove test data, private credentials and unlicensed material before adding the delivery destination.
Run an authorized checkout test with an identity that represents a buyer, then inspect both the payment result and fulfillment result. A browser return page is not evidence of a captured payment by itself. Exercise purchase recovery and a delivery retry. Before announcing the product, keep a record of the terms, the version being sold and the recovery instructions your staff will give a customer.
Compare the operating model, not just the headline fee
Manual ticket selling can suit occasional custom work, but staff must reconcile each payment and fulfill each promise. A percentage marketplace may include discovery, billing, tax or hosting services you would otherwise operate. Cartcord's flat server plan and direct seller PayPal checkout serve a different workflow. Calculate the cost of the features you actually need instead of treating every percentage or subscription as interchangeable.
Include payment processing, currency conversion, hosting, refunds and support time in the comparison. Cartcord taking zero sales commission does not remove those costs or make Cartcord the merchant of record. Check the current plan's limits and provider eligibility for your particular product. Choose the route that meets the buyer's delivery and recovery needs at the volume you can realistically support.
| Responsibility | Manual ticket workflow | Cartcord released workflow |
|---|---|---|
| Payment confirmation | Staff reconcile the correct merchant transaction | Provider confirmation is checked before configured delivery |
| Fulfillment | Staff send the resource or complete the promised service | Configured file, link, key or role delivery is attempted; manual work still needs staff |
| Recovery | Staff locate the purchase and determine what was delivered | Original-account purchase recovery and recorded delivery results help investigate failures |
| Cost | Account for processor charges, tools and staff time | Account for the store plan, processor charges, hosting and support |
Compare your monthly cost scenarios
Enter your actual fees. These are editable USD scenarios, not provider quotes. Include processor charges in both scenarios. Compare equivalent services and permitted products; required platform checkout still applies.
Enter every fee, including zero where applicable. Use non-negative amounts, whole orders and percentages up to 100.
Taxes, refunds, disputes, conversion, payout and support costs need separate review. Cartcord sales commission is 0%; the store plan and processor costs remain.
Questions
Can I sell a private link instead of a file?
Yes. Link delivery sends the URL you configured.
Who pays the PayPal fee?
PayPal charges its usual processing fee. Cartcord adds 0%.
How many products are on Free?
3 products and 3 orders a month.
Do buyers need a Cartcord password?
No. They use Discord and PayPal.