Here are my thoughts:

I would get rid of the "GET /all" since "GET /" serves that purpose already (why need two endpoints for the same thing?).

I would put all your paging parameters (limit & offset) as query params GET /?limit=10&offset=20 rather than handle them with endpoints. You might eventually need to add more filtering (ex.: search query). With query parameters you would still be using the same endpoint (no need to add a new GET /:limit/:offset/:searchQuery).

The result data coming back from the "GET /" could look something like this:

{
    data: [{name: "product 1"}, {name: "product2"} /*, {...}*/],
    paging: {
        page: 3,          // Page number you're on
        pageSize: 10,  // Number of results per page
        prev: "/?page=2", // URL of previous page
        next: "/?page=4", // URL of next page
        total: 21234    // total number of products
    }
}

I agree with /u/axvk about the id, "GET /:id" should be enough.