Fix DoesNotExist: Product matching query does not exist. in Django

This error means .get() was called on a queryset but no row matched the filter criteria. Fix it by using get_object_or_404() for views that should return a 404 page, wrapping .get() in a try/except block, or using .filter().first() which returns None instead of raising an exception when no match is found.

Reading the Stack Trace

Here's what each line means:

• File "/app/products/views.py", line 11, in product_detail: The view calls Product.objects.get(slug=slug) with a slug value that does not match any row in the database.
• File "/venv/lib/python3.11/site-packages/django/db/models/query.py", line 637, in get: Django's QuerySet.get() raises DoesNotExist when zero rows match the filter. It also raises MultipleObjectsReturned if more than one row matches.
• products.models.Product.DoesNotExist: Product matching query does not exist.: No Product row in the database has the requested slug value.

Common Causes

def product_detail(request, slug):
    product = Product.objects.get(slug=slug)  # Crashes if slug not found
    return render(request, 'products/detail.html', {'product': product})

def product_detail(request, slug):
    # Does not filter by is_published, so published URLs may break
    product = Product.objects.get(slug=slug, is_published=True)

# URL: /products/My-Product/
# Database slug: my-product
product = Product.objects.get(slug='My-Product')  # Case mismatch

The Fix

Use get_object_or_404() which catches DoesNotExist and returns a proper 404 response. This is Django's idiomatic pattern for detail views. For non-view code, use try/except or .filter().first() depending on whether the absence is expected.

def product_detail(request, slug):
    product = Product.objects.get(slug=slug)
    return render(request, 'products/detail.html', {'product': product})

from django.shortcuts import get_object_or_404

def product_detail(request, slug):
    product = get_object_or_404(Product, slug=slug)
    return render(request, 'products/detail.html', {'product': product})

# Alternative: try/except for custom handling
# from django.http import Http404
# def product_detail(request, slug):
#     try:
#         product = Product.objects.get(slug=slug)
#     except Product.DoesNotExist:
#         raise Http404('Product not found')
#     return render(request, 'products/detail.html', {'product': product})

Testing the Fix

import pytest
from django.test import TestCase, Client
from products.models import Product


class TestProductDetail(TestCase):
    def setUp(self):
        self.client = Client()
        self.product = Product.objects.create(
            name='Test Widget',
            slug='test-widget',
            price=9.99,
        )

    def test_existing_product_returns_200(self):
        response = self.client.get('/products/test-widget/')
        assert response.status_code == 200
        self.assertContains(response, 'Test Widget')

    def test_nonexistent_product_returns_404(self):
        response = self.client.get('/products/does-not-exist/')
        assert response.status_code == 404

    def test_deleted_product_returns_404(self):
        self.product.delete()
        response = self.client.get('/products/test-widget/')
        assert response.status_code == 404

Run your tests:

pytest

Pushing Through CI/CD

git checkout -b fix/doesnotexist-product-detail,git add products/views.py,git commit -m "fix: use get_object_or_404 to return 404 for missing products",git push origin fix/doesnotexist-product-detail

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:15
        env:
          POSTGRES_DB: test_db
          POSTGRES_USER: postgres
          POSTGRES_PASSWORD: postgres
        ports:
          - 5432:5432
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.11'
          cache: 'pip'
      - run: pip install -r requirements.txt
      - run: pytest --tb=short -q

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

pip install bugstack

import bugstack

bugstack.init(api_key=os.environ["BUGSTACK_API_KEY"])

Deploying the Fix (Manual Path)

1. Run the full test suite locally to confirm 404 handling works.
2. Open a pull request with the view fix.
3. Wait for CI checks to pass on the PR.
4. Have a teammate review and approve the PR.
5. Merge to main and verify 404 pages render correctly in staging.

Frequently Asked Questions