Answers for buyers,
sellers & builders.

Open a product page, review its details and choose the available purchase or checkout option. Sign in as a buyer when required, confirm the license or package, and complete payment using the methods enabled by the marketplace.

A buyer account is normally required to place orders, access licenses, view purchases, receive notifications and download files securely.

After signing in, open your buyer dashboard and use the Purchases, Orders or Licenses sections to review completed orders and available product access.

Read the license options on the product page and choose according to how you plan to use the product. If the usage rights are unclear, contact the seller or support before purchasing.

Yes. Use the available messaging or support options to ask about compatibility, installation requirements, features, licensing or seller support before placing your order.

Review the technology stack, server requirements, version compatibility, included documentation, product update history, seller support period and license terms.

Eligible purchases are delivered through the secured buyer area. Access depends on the order status, license and current approved product version.

Sellers may publish newer versions through the marketplace version system. Availability of future versions depends on the product and license terms shown on the listing.

For manual payment methods, submit the required reference or proof. The order remains pending until the marketplace verifies it and updates the payment status.

Start with the seller support or marketplace chat, include your order details and explain the issue clearly. For account, payment or platform problems, use the Contact page or live support.

Open the Licenses section in your buyer dashboard. The marketplace records license access against eligible paid orders and products.

If the product license supports domain assignment, the buyer license area can provide a domain update option. Follow the product-specific terms before changing a licensed domain.

No. License scope can vary by product and package. Always use the rights shown on the specific product and checkout flow rather than assuming all listings use identical terms.

Approved versions are associated with the product. Eligible buyers can access the current version through their secured purchase or download area according to the license.

Version availability is controlled by the product and marketplace workflow. Keep your own legitimate project backups and review the release information before replacing production files.

The current version can be displayed on the product listing and product detail page together with the category and other product metadata.

A version release should use a clear version number and provide relevant update information so buyers understand compatibility, fixes and meaningful changes.

Yes. A submitted product version can remain pending or be rejected when it does not meet marketplace requirements or needs correction.

Back up your website or app, review the seller documentation and changelog, test the update in a staging environment when possible, and only then deploy it to production.

Use marketplace messaging for product-specific questions and contact PutinCode support for account, order or platform-level license access issues.

PutinCode is a curated marketplace for source code, SaaS products, web apps, mobile apps, UI assets and developer services. Buyers can evaluate product information, licensing and updates before purchase, while approved sellers can publish and support their digital products.

The marketplace can include PHP and Laravel scripts, SaaS applications, React or Flutter projects, mobile apps, APIs, plugins, UI kits, automation tools and other launch-ready digital products approved by the platform.

Products are grouped by category, technology and searchable keywords. Featured products can be highlighted by the marketplace, while product pages show the current version, seller, pricing, media, license information and available updates.

A verified or approved status means the listing passed the marketplace moderation workflow for publication. Buyers should still review requirements, documentation, compatibility and license terms for their own project before purchasing.

Yes. Use the marketplace search and category filters to look for technologies such as PHP, Laravel, React, Flutter, SaaS, APIs and other product types.

No. The platform can also list digital products, implementation services, UI resources, setup help, product updates and other developer-focused offerings configured by the marketplace.

Featured placement is controlled by marketplace moderation. Featured items can appear in higher-visibility sections such as the home hero or curated product collections.

Yes. The public marketplace, account areas, messages and support interfaces are designed to work on modern mobile and desktop browsers.

Check the marketplace, media hub and official social channels listed in the footer. The media page can show new videos, product showcases and links published by the admin.

Use the footer links for Terms, Privacy, FAQ and other published CMS pages. These pages explain marketplace rules, privacy practices and important account information.

It is a public page that collects official social links, uploaded media cards, product highlights and playable YouTube content configured by the marketplace admin.

Yes. When the admin adds a valid YouTube URL and enables embedding, the Media page displays the video in an embedded player.

The admin can upload a platform icon and preview image, add the official profile or media link and publish the card. Visitors can view the preview and open the official destination.

Yes. Social platform name, title, profile URL, media URL, icon, preview image, visibility, embedding option and sort order are stored in the database and managed by the admin.

Visible social channels can appear in the website footer and on the dedicated Media & Social Hub page.

Use the Contact page, live support widget or the support channel shown on the site. Provide your account or order context without sharing passwords or other unnecessary secrets.

Include a concise subject, the relevant product or order reference when applicable, what you expected, what happened and any safe diagnostic details that help reproduce the issue.

Yes. The public Contact page accepts enquiries with a name, valid email, topic and message, and stores them in the admin support queue.

Messages are stored in the database with a status such as new, read, replied or closed. Admins can review and update the queue from the settings area.

Use links published directly in the PutinCode footer or Media & Social Hub. These links are controlled by the site admin and are the safest place to find official channels.

Create an account using the seller flow, complete the requested profile information and use the seller dashboard to prepare your first listing. Product publication remains subject to marketplace moderation.

Use a clear product name, accurate description, technology details, version number, requirements, pricing, license information, screenshots or media, documentation and realistic support terms.

Yes, where enabled. Product galleries can contain multiple images, and visibility can be controlled for marketplace presentation.

Submitted products enter the moderation workflow. An admin can approve, reject, hide or feature a listing after reviewing its information and marketplace suitability.

Yes. Sellers can submit product versions, and marketplace moderation can approve the new version before it becomes the current public release.

Paid orders can generate seller earnings after the marketplace commission configured by the admin. Sellers can review earnings and eligible withdrawal information from their dashboard.

The platform supports global commission settings and can also store seller-specific commission values when configured by the admin.

Respond through marketplace messages, provide concise setup instructions and keep product documentation current. Avoid requesting unnecessary sensitive buyer information.

Accurate screenshots, detailed requirements, clear pricing, realistic claims, maintained versions, responsive support and professional documentation improve buyer confidence.

Yes, when the marketplace service module is enabled. Service requests can be managed separately from downloadable product orders.