Feature Request: Multiple PR contributors payout distribution

[skndash96]

Node.js version

24

Database and its version

16.2

Operating system name and version

Linux

Browser name

No response

What happended?

As per the documentation, the GET cart endpoint supports returning items.variant.inventory_quantity
but it doesn't return. See actual behaviour section for the actual request and response.

Expected behavior

Expected behaviour is that the GET cart API endpoint returns the items.variant.inventory_quantity when requests, but it ignores this field.

Actual behavior

  return await sdk.client
    .fetch<HttpTypes.StoreCartResponse>(`/store/carts/${id}`, {
      method: "GET",
      query: {
        fields:
          "*items, *region, *items.product, *items.variant, +items.variant.inventory_quantity, *items.thumbnail, *items.metadata, +items.total, *promotions, +shipping_methods.name",
      },
      headers,
      next,
      // cache: "force-cache",
    })

I tried the following:

*items.variant, +items.variant.inventory_quantity
The field is missing in the response

*items.variant.inventory_quantity
error: Entity 'ProductVariant' does not have property 'inventory_quantity'
ValidationError: Entity 'ProductVariant' does not have property 'inventory_quantity'

*items.variants.inventory_quantity and many other trials
TypeError: Cannot read properties of undefined (reading 'strategy')

What's the proper way to retrieve inventory_quantity during cart GET?
Why do I need this? Because I have to prevent this flow:

1. A customer adds a product to the cart.
2. Abandon cart for a day
3. The product becomes out of stock
4. Customer comes back and checkouts
5. No error until the customer clicks Place Order

So i have to prevent this.

[bountic-bot]

💰 Bountic Ledger

Issue: skndash96/bountic#12
Status: 🟢 OPEN
Total Bounty: $10.00 USDC

Leaderboard

Rank	Funder	Contribution
1	Anonymous	$10.00

---

This comment is managed by Bountic and stays pinned for quick tracking.

• Issue Page: Open Bounty Dashboard

[Ramanand-Shirbhate]

/attempt

Hi there! I have strong experience with this stack and would love to take this on. I will begin setting up my environment and auditing the required modules immediately.

[Ramanand-Shirbhate]

Hey @skndash96, I've just opened PR #14 to resolve this.

I implemented the split logic using the GitHub API to parse the commit trailers dynamically. This avoids any need for a database migration while still safely handling the floating-point math for the payouts.

Let me know if you'd like any adjustments!

[snakefood3232]

The issue is that you need items.variant.inventory_quantity in the cart API response to prevent out-of-stock checkouts. I'd handle this by checking the database schema and resolver logic to ensure inventory_quantity is properly mapped and fetched. If not present, it may need schema adjustments or resolver modifications to expose it. Can have a PR up in 2 days. I've dealt with similar issues when integrating API response fields in e-commerce platforms, so I'm confident in efficiently resolving this for you.

[jshaofa-ui]

Interest in Contributing: Multiple PR Contributors Payout Distribution

I'm interested in implementing this feature for the bountic platform. This is a critical feature for any bounty platform that wants to support collaborative development.

Proposed Approach

1. Multi-contributor tracking: Extend the existing cart/claim system to support multiple contributors per bounty
2. Payout split configuration: Allow bounty posters to define split percentages (e.g., 60/40, equal split)
3. PR attribution: Link multiple PRs to a single bounty with individual contribution tracking
4. Escrow distribution: Modify the payout flow to distribute funds across multiple wallets/accounts

Technical Considerations

• Database schema changes for multi-contributor relationships
• UI updates for configuring payout splits
• Backend logic for proportional payout calculation
• Integration with existing payment/bounty system

Files to Touch

• Cart/claim models and services
• Payout distribution logic
• API endpoints for multi-contributor claims
• Frontend components for split configuration

I can start with a draft PR within 48 hours.

[Ramanand-Shirbhate]

Hey @skndash56, just following up on PR #14!

I noticed some of the other comments are referencing an e-commerce inventory_quantity bug—I assume that was a copy-paste artifact in the issue description?

To reiterate for the actual feature request (Multiple PR Payouts): My PR resolves this without requiring any complex database migrations or escrow schema changes. It simply parses standard GitHub commit trailers (e.g., Co-authored-by) via the API and handles the floating-point payout math dynamically.

Let me know if you need any adjustments to the math logic!

[Vishal8736]

I'm available to work on this issue. Please assign it to me if possible. Thanks!

Regards,
mr.vishal_hacker

[Vishal8736]

Hey, I'd like to work on this issue #12. Can you assign it to me?

Regards,
mr.vishal_hacker

[ixhxpns]

I am claiming this task: Implement multi-contributor payout logic with atomic distribution. Working on the implementation now.

[jshaofa-ui]

Multiple PR Contributors Payout Distribution - Implementation Proposal

This is a great feature for bountic! Here's my implementation approach:

Architecture

1. Contribution Tracking

   • Link multiple PRs to a single bounty
   • Track contribution weight per PR (based on lines changed, complexity, review scores)
   • Support manual weight adjustment by maintainers

2. Payout Calculation Engine

   • Proportional distribution based on contribution weights
   • Minimum payout threshold configuration
   • Support for flat-rate + bonus models

3. UI/UX

   • Bounty dashboard showing all linked PRs
   • Contribution breakdown visualization
   • Payout preview before distribution

4. Smart Contract Integration (if applicable)

   • Multi-sig payout transactions
   • Escrow release on PR merge
   • Dispute resolution mechanism

Technical Stack

• Backend: Node.js/TypeScript or Python
• Database: PostgreSQL for contribution tracking
• Frontend: React/Vue for dashboard
• Optional: Solidity smart contracts for on-chain payouts

Timeline

• Core contribution tracking: 3-4 days
• Payout calculation engine: 2-3 days
• UI implementation: 3-4 days
• Testing and documentation: 2 days
• Total: ~2 weeks

Why Me

• Experience building bounty/reward platforms
• Full-stack development capabilities
• Familiar with contribution analysis and metrics

Would love to discuss this further and start with a prototype.