What kind of products will CodingRepo sell?
CodingRepo is focused on practical software and business technology products. That includes WordPress plugins, scripts, automation tools, web apps, templates, starter kits, developer utilities, documentation packages, and other downloadable products that solve real technical or business problems.
CodingRepo is not intended to be a general file marketplace. Product listings should be clear, useful, packaged for buyers, and tied to a real software or business workflow.
Do I need an account to buy a product?
Yes. CodingRepo uses accounts so purchases, order history, downloadable files, invoices, license keys when enabled, reviews, and support information can stay tied to the buyer who completed checkout.
Use the same account when returning later. The dashboard and WooCommerce account pages are the supported places for order and download access after purchase.
Where do downloads show up after purchase?
Purchased products with downloadable files appear in the buyer dashboard after checkout. The Downloads view shows product files, file names, file type and size when available, invoice links, product links, and license key details when the seller enabled license generation for that product.
Downloads are served through protected dashboard download URLs. Buyers should be signed in with the account used for checkout.
What should I check before buying?
Review the product listing before checkout. Check the description, price, included files, screenshots, feature list, platform or version requirements, support policy, future update terms, live preview link if provided, and whether license keys are generated for the product.
If something important is unclear, use the available support or contact information before purchasing.
Are license keys included with every product?
No. License keys are optional per listing. Sellers can enable the Generate License Keys setting for a product. When enabled, completed purchases receive a unique license key that can be used with the CodingRepo license API for activation, deactivation, and status checks.
If a product does not have licensing enabled, the buyer dashboard will not show a license key for that purchase.
How does product review work?
Product submissions can be held for review before publication. The submission is saved with its listing details, files, images, category request, support settings, price, and selected review add-ons. Non-admin and non-moderator submissions can be moved to pending review when approval is required.
Review is intended to check that the product is appropriate for CodingRepo, complete enough to evaluate, and packaged with the required marketplace details. Review does not guarantee that every product will be approved.
What paid submission add-ons are available?
The current submission flow supports two optional paid add-ons: Featured Promotion and Expedited Review. Each add-on is priced at $50 in the local code. If selected, the listing is saved and the add-on is added to WooCommerce checkout as part of the submission flow.
- Featured Promotion marks the listing for featured treatment after the add-on order is paid.
- Expedited Review marks the listing as an expedited review request after the add-on order is paid.
Both add-ons are optional. Basic submission can remain unchecked.
Does expedited review guarantee approval?
No. Expedited Review is a priority review add-on, not an approval guarantee. A product can still be delayed, returned for changes, or rejected if the listing is incomplete, files are not allowed, images are missing, required product details are unclear, or the submission does not fit CodingRepo requirements.
Can I upload a product from mobile?
No. The product-upload page is intentionally blocked on mobile and tablet devices. Sellers should use a desktop or laptop so they can complete the full form, upload images and product files, set support details, choose category information, and review all required fields before submission.
What product information is required?
The submission flow requires a buyer-facing description, feature details, a sell price, and product files. The form also supports product images, banner image, screenshots, description images, live preview URL, category request, managed attributes such as platform or version details, support and future-update settings, and optional license-key generation.
Descriptions and feature text have a 5,000 character plain-text limit in the current validation code.
What images are required for a product?
The upload form separates product imagery by use case:
- A required dark/default square product card image. The guidance targets a 1024 x 1024 export.
- An optional light-mode square product image, also intended for square product cards.
- A product-page banner image. The guidance targets 1600 x 720 and recommends keeping the focal area near the center.
- Screenshot gallery images for product inspection.
- Optional product description images for longer inline walkthroughs inside the product content area.
What file types are allowed?
The current product file field allows ZIP, PDF, TXT, and MD files. ZIP files are supported for completed code packages, while PDF, TXT, and MD files can be used for documentation or related buyer-facing files.
The product file field allows up to 10 files, with a 256 MB max file size per file in the current field configuration. Uploaded product files are filtered to the allowed types and moved into private product storage for protected delivery.
How does support information work?
Sellers can enter product-specific support policy text and support contact routes. The current fields support a support URL, support phone, WhatsApp number, SMS number, and support email. Phone, WhatsApp, and SMS display depends on the matching enabled toggles.
The final product support block is built from those values and shown with the listing when support information is available.
Can sellers offer paid support or paid updates?
Yes. The product submission data supports future-update modes and support entitlement modes. Paid modes store a price; non-paid modes store the price as zero. Sellers can also offer an Extended Support Add-On when support is configured as a paid yearly entitlement.
Support and update promises should be written clearly in the listing so buyers understand what is included, what costs extra, and what is outside support scope.
Can sellers include demos or external support links?
Yes, when relevant. Sellers can add an optional Demo / Live Preview URL. If provided, the product page can show a Live Preview button that opens the demo inside a CodingRepo preview frame. Sellers can also provide a support URL for documentation, a support portal, setup instructions, or a product knowledge base.
External links should support the product listing. They should not be misleading, unrelated, or used to bypass CodingRepo checkout.
What should I avoid uploading or including?
Do not upload or publish passwords, API keys, private tokens, internal credentials, customer data, unrelated files, suspicious code, misleading screenshots, unfinished drafts, unsupported file types, or files that do not match the listing.
Product packages should be clean, versioned where possible, and ready for buyer review and download.
What can buyers manage from the dashboard?
The buyer dashboard includes areas for downloads, invoices, favorites, reviews, and account activity. Purchased products with files appear in Downloads after checkout. Buyers can also view invoices, open product pages, download available files, copy license keys when present, and write or view product reviews.
What if I purchased a product but do not see it?
First confirm that you are signed in with the same account used during checkout. Then check the order status, the dashboard Downloads view, and the Orders or invoice area. Downloads are tied to completed marketplace purchases and protected file records.
If the purchase still does not appear, contact support with the account email, order number, product name, and any payment confirmation details.
Where are invoices and order history?
Order history is available through the account Orders page, which shows order number, date, status, total, and actions. The CodingRepo dashboard Downloads area also includes an invoices view for purchased products.
Can buyers review products?
Yes. The dashboard Downloads view includes a product review area. Buyers can open the product review section from purchased products and either write a review or view an existing review status when one already exists.
What makes a product acceptable for CodingRepo?
A strong CodingRepo product is useful, clearly described, priced accurately, assigned to the closest category, packaged with allowed files, supported by required images, and honest about platform requirements, licensing, support, and updates.
Software products should be ready for review and should not include private credentials, unrelated files, or misleading claims.
Can CodingRepo reject a product?
Yes. CodingRepo may reject or delay products that are incomplete, misleading, unsafe, poorly documented, missing required files or images, uploaded with unsupported files, unclear in purpose, or not suitable for the marketplace direction.
Can I request a new category?
Yes. The upload form includes an Other Category / Sub Cat Request field. Sellers should choose the closest existing category first, then use the request field only when the current categories do not fit. The request is saved with the product and reviewed during approval.
Can a product be edited after submission?
Editing depends on the current product status and dashboard capabilities. If a product needs changes before approval, the seller may be asked to update the listing or assets. Sellers should submit accurate product information the first time to avoid review delays.
What is CodingRepo built around?
CodingRepo is built around software, development, automation, and business technology products. The marketplace supports buyer flows for WooCommerce checkout, protected downloadable files, dashboards, invoices, optional license keys, support expectations, demos, product reviews, and seller review workflows.